Menu
SkillsMP has collected 61 skills from caezium/skills. Open a skill to review its source and details.
Showing 40 of 61 collected skills.
Orchestrate Henry's long-running engineering and research work across recall, consultation, specifications, verification, worker fleets, evidence trails, handoffs, and reflection. Use when work spans sessions or machines, needs autonomous agents, crosses…
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding…
Implement a piece of work based on a spec or set of tickets.
Install a freshly authored skill into ~/skills/ (the source-of-truth repo), record its provenance, validate it, and symlink it into active agent directories. Use after creating a SKILL.md, when finishing an anthropic-skill-creator session, or when the user…
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants,…
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available evidence sources, searches each relevant category, and returns a cited read on decisions and tradeoffs. Use how…
Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.
Create, improve, and evaluate portable or Claude-oriented agent skills with Anthropic's skill-authoring workflow. Use when drafting or optimizing a non-Codex-system skill, running skill evals, benchmarking behavior, or improving trigger descriptions. Codex's…
Find what a code, schema, API, config, or behavior change could break beyond its visible diff, then prove the safety-critical assumption with real code. Use whenever the user asks what could break, requests a blast-radius review, or distrusts a deceptively…
Create a project-local skill that launches and drives the real app like a user, captures durable proof, and cleans up safely. Use whenever a repo lacks a scripted way to verify UI, CLI, desktop, mobile, API, or service behavior end to end.
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict…
A relentless interview to sharpen a plan or design.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Compact the current conversation into a handoff document for another agent to pick up.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Run an adversarial review of code or a diff through independent reviewers, then lead-judge consensus, disagreements, and false positives. Use when the user asks to interrogate, challenge, stress-test, find blind spots, perform multi-model review, or when…
Autonomous, disciplined Kaggle competition workflow — the loop that took Playground S6E6 to 19th/2742 (top 0.7%). Use when working a Kaggle competition (Playground/tabular especially): building a model zoo, stacking, deciding what to submit, choosing final…
Audit and repair a project verification skill and its feature map against current source and live behavior. Use whenever the user asks to maintain, refresh, or audit a verify skill, its harness, or its user-facing feature coverage.
Build the smallest rerunnable tool that performs or proves non-trivial work. Use for migrations, repetitive edits, analyses, audits, generators, or delegated campaigns where hand work would drift or be hard to review.
Protect reasoning quality when files, histories, logs, screenshots, search results, or worker output are large. Use before bulk reads or fan-out and whenever the active context is filling with payload rather than decisions.
Prove completed work against the real artifact before declaring success. Use after any implementation, migration, delegated task, configuration change, or fix where compilation, self-report, cached output, or file existence could hide failure.
Break multi-step work into small units that each end in a checkable green state. Use for sweeps, migrations, repeated edits, long agent runs, or commit/PR stacks where batching would hide the first failure.
Reconstruct recent working context from scoped agent history, project records, and live repository state. Use whenever the user asks to catch up, resume prior work, remember what happened, or continue work whose earlier agent context is missing.
Review the active session through judgment, tooling, and divergent lenses, then propose durable skill edits or structural backlog items. Use when the user asks to reflect, wants better agent behavior from a session, or when `henry-mode` closes expensive,…
Keep an auditable decision trail for long-running, autonomous, delegated, or multi-phase work. Use whenever a human will review the result after stepping away and needs decisions, evidence, pivots, and verification without rereading the full transcript.
Fan out a task across N independent workers, drain every wave, and return one evidenced report. Use when the user asks to swarm, parallelize, race approaches, run a gauntlet, divide exhaustive coverage, or when `henry-mode` reaches a settled parallel-work…
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Consult the user before making consequential product or design decisions, drafting a substantive plan or document, or implementing a nontrivial change whose direction is not settled. Use automatically whenever meaningful choices about purpose, users, scope,…
Plan and run a custom video-editing pipeline from a plain-language brief — clip, cut, trim, montage, reframe, or caption any footage. Use this whenever the user wants to edit or auto-clip video: make a highlight reel, a montage, a supercut, a beat-synced…
Pull Henry's Dayflow activity data (what he actually worked on, day by day, card by card, with accurate hours) straight from Dayflow's local SQLite DB — read-only. Use whenever Henry asks to check his Dayflow, compute real work hours, build a weekly/daily…
Restate the last message in plain human language, with no jargon.
Sync caezium/Dayflow fork with upstream JerryZLiu/Dayflow. Rebases private-hardening onto upstream/main, auto-skips known-droppable commits, runs audit + Debug build, then stops at a pre-install checkpoint and waits for the user to say "install". Use when the…