From starlight-intelligence-system
Scans exports, files, and vault batches for credentials, API keys, and sensitive data before they leave the local machine. Blocks export if secrets are found.
How this skill is triggered — by the user, by Claude, or both
Slash command
/starlight-intelligence-system:secret-detectorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Nothing sensitive exits the local machine without explicit human awareness.
Nothing sensitive exits the local machine without explicit human awareness.
~/.starlight/ to an external destinationScans content for credential patterns, personal identifiers, and sensitive data before it leaves the local machine. Blocks export if secrets are found. Never auto-redacts — always surfaces findings to the user for an explicit decision.
Receive content blob pending export
Run pattern detection against the full content:
| Pattern | Example | Action on match |
|---|---|---|
| API keys | sk-..., pk_..., ghp_..., xoxb-... | BLOCK + report |
| Private keys | -----BEGIN PRIVATE KEY----- | BLOCK + report |
| Passwords in config | password=, passwd=, secret= | BLOCK + report |
| Email addresses | [email protected] in unexpected context | WARN + report |
| Phone numbers | +1-555-..., formatted phone patterns | WARN + report |
| Credit card patterns | 16-digit sequences with separators | BLOCK + report |
| Government IDs | SSN patterns, national ID formats | BLOCK + report |
If BLOCK patterns found: halt export, generate SECRET_SCAN_REPORT.md, present to user
If WARN patterns found: present to user with option to proceed or redact
If clean: return APPROVED for export
/security/SECRET_SCAN_REPORT.mdprivate-public-split for structural classification; permission-gate for the approval flownpx claudepluginhub frankxai/starlight-intelligence-systemGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.