Loading...
Loading...
Found 92 Skills
[Tooling & Meta] Save memory checkpoint to preserve analysis context
Assess a codebase's readiness for autonomous agent development and provide tailored recommendations. Use when asked to evaluate how well a project supports unattended agent execution, assess development practices for agent autonomy, audit infrastructure for agent reliability, or improve a codebase for autonomous agent workflows. Triggers on requests like "assess this project for agent readiness", "how autonomous-ready is this codebase", "evaluate agent infrastructure", or "improve development practices for agents".
Reconstruct and narrate the current development context from contextual commits. Run at session start, when resuming work, or when switching branches. Produces a brief, conversational summary of where things stand.
Git operations expert for branching, rebasing, conflicts, and workflows
Use when the workflow feels too complex, has accumulated cruft, or has redundant steps and overlapping tools that need consolidation.
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.
Use when multiple workflows duplicate the same operational logic, when deciding what belongs in actions vs shared services, or when refactoring repeated operational blocks across domain flows. Use when adding new features that share mechanics with existing ones.
Opens a new jackin' feature or idea as a roadmap item draft plus an early pull request, without writing any code. Use when the operator runs /jackin-dev:propose.
Configure Exa local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Exa. Trigger with phrases like "exa dev setup", "exa local development", "exa dev environment", "develop with exa".
Capture and persist lessons learned from a session to compound knowledge over time. Triggers on "/lessons-learned", "what did we learn", "save lessons", "update skills with what we learned", or at the end of a complex multi-session task. PROACTIVE USE: This skill should also be suggested or invoked (1) when resuming from context compaction (the previous context likely contained unrecorded lessons), (2) after resolving a non-trivial bug or debugging session, (3) after significant friction or failed approaches that yielded insight, (4) after a council-of-bots review that surfaced fixes. Identifies reusable patterns, bug fixes, workflow insights, and tool quirks, then persists them to the right places: auto-memory (project-specific), skill files (reusable across projects), or both.
Learn about your OMC usage patterns and get personalized recommendations