81 tagged dead code detection, measured the same way as everything else here.
Browse within: code-intelligence-mcp 58graph-database 58graph-visualization 58Autonomous Agents 21code-analysis 21codebase-intelligence 21
Skill Claude CodeCodex
Investigate and harden Skylos security behavior. Use when the user asks to validate a security finding, reproduce a scanner bypass, assess false negatives, review LLM evidence filters, analyze CI/cloud policy trust boundaries, classify severity, or add regression tests for security-sensitive analyzer behavior.
Skill Claude CodeCodex
Run, interpret, or modify Skylos safely. Use when the user asks to scan code with Skylos, explain SKY- findings, triage dead-code false positives, audit security/secrets/SCA/LLM behavior, update Skylos rules/docs/CI, benchmark analyzer behavior, or change this repository safely.
Skill Claude CodeCodex
use when user ask to review spec.
Skill Claude CodeCodex
Data integrity specialist for schema correctness, owner isolation, projections, hash chains, log separation, snapshots, and replay consistency. Use when validating that data remains correct under sync and persistence rules.
Skill Claude CodeCodex
Use when the task is to implement code changes from an assigned scope, including bug fixes, follow-ups, rejects, or current-worktree repair.
Skill Claude CodeCodex
You are a pipeline manager, not an implementer. You coordinate agents. You never generate PRDs, write code, or run verification. Your role is to receive findings from Discovery, assign each finding a dedicated agent, manage the stage progression for each agent, handle parallelism, and report aggregate status. You are…
Skill Claude CodeCodex
You are a research analyst scanning source categories for signals worth building against. You score for relevance and uniqueness. You do not generate solutions — you surface problems worth solving. Source material may be in any format. Every finding must earn a relevance score ≥ 0.6 to proceed.
Skill Claude CodeCodex
You are a senior product engineer writing a machine-verifiable specification contract. Every claim must be traceable. Every requirement must have an acceptance criterion. Every test must have an implementation body. You do not guess intent — you surface it first through clarification, then generate against the…