Skills are reusable operating procedures for the harness. Agents can invoke them to follow a repeatable workflow instead of improvising.
| Skill | Folder | Purpose |
|---|---|---|
| architect | agent-architect | Software architecture specialist for system design, scalability, and technical decision-making. Use PROACTIVELY when planning new features, refactoring large systems, or making architectural decisions. |
| build-error-resolver | agent-build-error-resolver | Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly. |
| doc-updater | agent-doc-updater | Documentation and codemap specialist. Use PROACTIVELY for updating codemaps and documentation. Runs /update-codemaps and /update-docs, generates docs/CODEMAPS/*, updates READMEs and guides. |
| e2e-runner | agent-e2e-runner | End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work. |
| planner | agent-planner | Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks. |
| refactor-cleaner | agent-refactor-cleaner | Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it. |
| code-reviewer | agent-reviewer | Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes. |
| security-reviewer | agent-security-reviewer | Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities. |
| tdd-guide | agent-tdd-guide | Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage. |
| gitnexus-cli | gitnexus-cli | Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki\ |
| gitnexus-debugging | gitnexus-debugging | Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug\ |
| gitnexus-exploring | gitnexus-exploring | Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow\ |
| gitnexus-guide | gitnexus-guide | Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?\ |
| gitnexus-impact-analysis | gitnexus-impact-analysis | Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?\ |
| gitnexus-refactoring | gitnexus-refactoring | Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file\ |
| macrodata-distill | macrodata-distill | Extract distilled actions and facts from today's conversations. Spawns sub-agents per conversation to avoid context blowup. |
| macrodata-dreamtime | macrodata-dreamtime | Deep nightly reflection. Self-improvement, research, pattern recognition. Runs in background with no user interaction. |
| macrodata-memory-maintenance | macrodata-memory-maintenance | End of day memory maintenance. Runs distillation, updates state files, prunes stale info. Runs in background with no user interaction. |
| macrodata-onboarding | macrodata-onboarding | Guide new users through macrodata setup. Creates identity, human profile, and workspace files. Use when get_context returns isFirstRun true, or user asks to set up their profile. |
| backend-patterns | ultraskill-backend-patterns | Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. |
| clickhouse-io | ultraskill-clickhouse-io | ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads. |
| coding-standards | ultraskill-coding-standards | Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development. |
| ultraskill-eval-harness | ultraskill-eval-harness | Eval Harness Skill |
| frontend-patterns | ultraskill-frontend-patterns | Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. |
| ultraskill-project-guidelines-example | ultraskill-project-guidelines-example | Project Guidelines Skill (Example) |
| security-review | ultraskill-security-review | Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns. |
| tdd-workflow | ultraskill-tdd-workflow | Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests. |
| ultraskill-verification-loop | ultraskill-verification-loop | Verification Loop Skill |
- agent-* skills cover planning, architecture, reviews, refactors, build-error resolution, end-to-end runs, docs, and TDD.
- gitnexus-* skills teach the agent how to index, query, debug, analyze impact, and refactor through GitNexus.
- macrodata-* skills keep persistent memory clean, useful, and ready for future sessions.
- ultraskill-* skills encode project standards for backend, frontend, security, ClickHouse, evaluation harnesses, TDD, and verification loops.