identify
Identify friction points, bottlenecks, bugs, and technical debt. Use for audits, debugging sessions, when something feels wrong, or before major work to surface hidden issues. This is the second system in the 5-system framework.
npx skills add majiayu000/claude-skill-registry --skill 2-identify-ioku24-autorankr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Identity System (Detection) > **Purpose:** Surface problems, friction, and bottlenecks before they compound. > **When to trigger:** Audits, debugging, pre-work analysis, or when something feels off. ## Detection Categories ### 1. Code Health Run these checks: - Type errors: `npx tsc --noEmit` - Build errors: `npm run build` - Lint issues: Check for warnings - Unused imports/variables - Circular dependencies ### 2. Performance Issues Look for: - Slow database queries (check Supabase logs) - Large bundle sizes - Unnecessary re-renders - N+1 query patterns - Missing indexes ### 3. User Experience Friction Identify: - Error states not handled gracefully - Loading states missing - Confusing user flows - Edge cases not covered - Poor error messages ### 4. Architecture Debt Spot: - Duplicated logic across files - Inconsistent patterns - Missing or premature abstractions - Tightly coupled components - God components/functions ### 5. Operational Gaps Find: - Missing error tracking/logging - No observability into failures - Manual processes that should be automated - Missing environment variables - Insecure configurations ### 6. Security Concerns Check for: - Exposed secrets or credentials
- Detection Categories
- 1. Code Health
- 2. Performance Issues
- 3. User Experience Friction
- 4. Architecture Debt
- 5. Operational Gaps
- 6. Security Concerns
- Detection Process
- Quick Scan (5 min)
- Deep Scan (30 min)
- Output Requirements
- Rules
- Transition
Run type check npx tsc --noEmit Check for build errors npm run build Look for TODOs and FIXMEs grep -r "TODO\|FIXME\|HACK\|XXX" src/
What does the identify skill do?
Identify friction points, bottlenecks, bugs, and technical debt. Use for audits, debugging sessions, when something feels wrong, or before major work to surface hidden issues. This is the second system in the 5-system framework.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill 2-identify-ioku24-autorankr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.