Agent Skill
2/7/2026

skill-check

Quality gate for skill development and sharing. Validates naming, description quality, and structure. Before sharing, scans for PII/secrets. Triggers on 'check this skill', 'validate skill', 'can I share this', 'scan for sharing'. Complements skill-creator (process) with validation (requirements). (user)

S
spm1001
0GitHub Stars
1Views
npx skills add spm1001/claude-suite

SKILL.md

Nameskill-check
DescriptionQuality gate for skill development and sharing. Validates naming, description quality, and structure. Before sharing, scans for PII/secrets. Triggers on 'check this skill', 'validate skill', 'can I share this', 'scan for sharing'. Complements skill-creator (process) with validation (requirements). (user)

trousse

Status

Robustness: Stable — used daily Works with: Claude Code (session lifecycle), any agent (skills) Install: git clone + install.sh Requires: Claude Code CLI (for hooks), none (for skills alone)

A toolkit for Claude Code (Anthropic's CLI coding assistant) that gives it session memory and specialized capabilities.

The Problem

Claude Code is stateless. Every time you start a session, Claude has no memory of what you worked on before — what was done, what's next, what to watch out for. If you're using Claude Code daily, you spend the first few minutes of every session re-explaining context.

What This Does

trousse solves this with two things:

A session protocol — shell hooks that fire automatically when Claude Code starts and stops. At startup, Claude sees a briefing: what you were working on, what the previous session accomplished, and what's ready to pick up. At close, it writes a handoff for the next session. The gap between sessions becomes a baton pass, not a cold start.

A skill drawer — a collection of slash commands (/diagram, /review, /filing, etc.) that teach Claude Code specialized workflows. Skills are SKILL.md files — structured instructions that Claude reads and follows. They're installed as symlinks into ~/.claude/skills/.

Quick Start

git clone https://github.com/spm1001/trousse ~/Repos/trousse
cd ~/Repos/trousse
./install.sh

Then restart Claude Code (/exitclaude).

Verify: ./install.sh --verify

Dependencies: jq (required — brew install jq on Mac, apt install jq on Linux).

What You Get

Session Lifecycle (automatic after install)

WhatWhenHow
Startup briefingEvery session startHook runs open-context.sh, shows outcomes and last session summary
Tactical remindersEvery promptHook shows current work step so Claude doesn't drift
/openOn demandRe-orient mid-session or after changing directories
/closeEnd of sessionReflect on work done, write handoff for next session

Skills (slash commands)

SkillWhat it does
/titans (or /review)Three-lens code review: hindsight, craft, foresight
/diagramCreate diagrams with iterative render-and-check
/screenshotCapture screen to verify changes
/filingOrganize files using PARA method
/pictureGenerate images with AI
/server-checkupLinux server audit and management
/github-cleanupAudit repos, find stale forks and secrets
/spriteManage Sprites.dev remote VMs
/setupInstall trousse on a new machine
/skill-forgeBuild and validate new skills
/skill-checkQuality gate for skill sharing

Companion Skills (loaded by other skills, not invoked directly)

SkillLoaded byPurpose
bon/openWork tracking across sessions (outcomes + actions)

How It Works

Directory Structure

trousse/
├── hooks/                  # Shell scripts that fire on Claude Code events
│   ├── session-start.sh    #   → runs open-context.sh at session start
│   ├── session-end.sh      #   → cleanup at session end
│   └── bon-tactical.sh     #   → injects current work step into every prompt
├── scripts/                # Utility scripts called by hooks and skills
│   ├── open-context.sh     #   → generates session briefing
│   ├── close-context.sh    #   → generates session handoff
│   ├── bon-read.sh         #   → fast jq reads from bon's data file
│   ├── claude-doctor.sh    #   → diagnose broken symlinks and config
│   ├── check-home.sh       #   → detect home directory issues
│   └── check-symlinks.sh   #   → verify symlink integrity
├── skills/                 # Skill definitions (SKILL.md files)
│   ├── open/               #   → session orientation
│   ├── close/              #   → session handoff
│   ├── titans/             #   → three-lens code review
│   ├── diagram/            #   → diagramming workflow
│   └── ...                 #   → (16 skills total)
├── references/             # Architecture docs (not loaded automatically)
│   ├── HANDOFF-CONTRACT.md #   → handoff format specification
│   ├── HOOKS_AND_SCRIPTS.md#   → hook architecture audit
│   └── ERROR_PATTERNS.md   #   → troubleshooting guide
├── tests/                  # pytest suite
├── install.sh              # Installer (creates symlinks, registers hooks)
└── CLAUDE.md               # Instructions Claude reads when working in this repo

Installation Mechanics

install.sh creates symlinks — it doesn't copy files:

  • Each skills/<name>/ directory gets symlinked to ~/.claude/skills/<name>
  • Each scripts/<name>.sh gets symlinked to ~/.claude/scripts/<name>.sh
  • Each hooks/<name>.sh gets symlinked to ~/.claude/hooks/<name>.sh
  • Hook events are registered in ~/.claude/settings.json

This means git pull updates everything — symlinks point to the repo, so changes take effect immediately (skills hot-reload; hooks and scripts are re-read each invocation).

The Handoff Protocol

When a session ends, /close writes a handoff file to ~/.claude/handoffs/<project>/. The next session's startup hook reads it and includes the summary in Claude's briefing. The handoff contains:

  • Done — what was accomplished
  • Next — suggested next steps
  • Gotchas — things to watch out for

The full specification is in references/HANDOFF-CONTRACT.md.

Optional Companion Tools

These are separate repos that add their own skills:

RepoWhat it adds
todoist-gtdGTD-flavored Todoist integration
garde-mangerSearch past Claude sessions
bonWork tracker CLI (outcomes + actions)

Troubleshooting

Skills don't appear? Restart required after first install. Run /exit then claude.

Hooks not firing? Run ./install.sh --verify to check symlinks. Run ~/.claude/scripts/claude-doctor.sh for diagnostics.

Need more help? See references/ERROR_PATTERNS.md for common issues and fixes.

Updating

cd ~/Repos/trousse && git pull
# Symlinks mean changes take effect immediately

Uninstalling

./install.sh --uninstall

Removes symlinks and hook registrations. Does not delete handoff history.

The Kitchen

Trousse is part of Batterie de Savoir — a suite of tools for AI-assisted knowledge work. See the full brigade and design principles for how the tools fit together.

Skills Info
Original Name:skill-checkAuthor:spm1001