capture-skill

Extract session discoveries and persist them as reusable skill files for Codex and Claude.

26|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/sburl/CrossCheck --skill capture-skill-sburl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-skill
Source: https://github.com/sburl/CrossCheck/tree/main/codex/skills/capture-skill
Command: npx skills add https://github.com/sburl/CrossCheck --skill capture-skill-sburl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distill non-obvious session insights into reusable skill files that auto-load in future sessions when the trigger conditions match.

Core Features & Use Cases

  • Discovers and captures unique findings from complex sessions
  • Persists skills to the Codex and Claude command caches for automatic loading
  • Enables quick reuse across projects and contexts

Quick Start

Use /capture-skill after you encounter a genuine discovery that improves workflows.

Frequently Asked Questions about capture-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save debugging workarounds as reusable commands for Claude and Codex?

To save debugging workarounds as reusable commands, extract the non-obvious session discovery and persist it as a structured skill file. The file is stored under ~/.claude/commands/ and ~/.codex/commands/ for automatic loading in future sessions.

What is the best way to capture project-pattern tolerances across different sessions?

The best way to capture project-pattern tolerances is to distill the session insight into a structured skill file containing a unique name, trigger conditions, a step-by-step solution, and verification steps, which auto-loads when matching conditions recur.

How does auto-loading captured skills work in future coding sessions?

Auto-loading captured skills works by storing the structured skill files directly in the local command caches at ~/.codex/commands/ and ~/.claude/commands/, enabling the AI to retrieve and apply the workflow automatically when trigger conditions match.

Do I need a specific environment setup to persist session discoveries as skill files?

You need local access to the ~/.codex/commands/ and ~/.claude/commands/ directories to persist session discoveries. The tool enforces a structured format with trigger conditions and verification steps to ensure the skill functions correctly.

When should I avoid capturing a session finding as a reusable skill?

You should avoid capturing a session finding as a skill if the discovery is obvious, does not improve workflows, or represents a one-time issue that will not recur across different tasks or debugging contexts.

What format does a captured workflow discovery need to follow for AI command caches?

A captured workflow discovery must follow a structured skill format that includes a unique name, a description, specific trigger conditions, a step-by-step solution, and verification steps before being stored in the AI command caches.