Claude Skills by jscraik

Generate closure proof with exact commands, outcomes, artifact paths, untested lanes, and residual risk. Use when work and review need a receipt before closeout, release, tracker movement, or handoff.

Plan how to implement one approved slice, including file targets, validation gates, rollback, and proof lanes. Use when a slice spec is accepted and the user needs the implementation order before code changes.

Analyze stale or conflicting lifecycle state by separating local, PR, CI, review, tracker, artifact, and session truth. Use when status is confused, work resumed after drift, evidence lanes disagree, or a closeout claim may be stale.

Plan a stuck, stale, or unsafe frame into a smaller viable direction with rollback and decision boundaries. Use when a migration, plan, PR, or implementation path is producing churn, conflicting claims, or unsafe scope.

Create a durable guardrail, validator, doc, eval, or skill-reference update from a verified failure or learning. Use when the user asks to capture learning, prevent recurrence, encode review feedback, or refresh stale guidance.

Review the completed slice for correctness, risk, evidence gaps, and next-stage blockers. Use when the user asks for review, PR readiness, risk assessment, blocker identification, or post-work verification.

Create one selected trace or tracker slice spec with acceptance criteria, constraints, validation, and exit conditions. Use when exactly one slice has been selected and needs a buildable contract before implementation planning.

Plan traceable work bullets that connect intent, evidence, acceptance, and proof gaps. Use when an idea or reframe needs decomposition into traceable work units before tracker or slice specification.

Plan tracker-ready slices with dependencies, labels, acceptance fields, and validation placeholders. Use when trace work needs Linear-ready or tracker-ready issue structure without actually mutating the tracker.

Build only the approved slice while preserving scope, unrelated worktree changes, and validation evidence. Use when an approved execution plan or explicit bounded task is ready for implementation.

Run structured AI code review as an advisory closeout gate for local diffs, PR branches, or commits when the user asks for autoreview, Codex review, second-model review, or pre-ship validation.

Check if a repository or agent-facing product surface is ready for AI coding agents. Use when you need to audit repo agent compatibility, review AGENTS.md, find missing test/build commands, evaluate docs quality, assess tool/action parity, or produce a file-evidence scorecard with specific fixes.

Create, review, and maintain gold-standard Skills SDK eval scenarios before internal evals, dry Tessl staging, or live private Tessl scoring. Use when creating or updating a skill, writing skill tests, adding eval cases, importing KnowledgeOS or Tessl suggestions, checking scenario drift, or hardening evals that are too easy.

Audit, rewrite, and validate README, runbook, code-doc, config-doc, package-evidence, and public trust-surface documentation against live repository evidence. Use when documentation needs proof-backed correction, reader-focused review, generated-document ownership, public-access checks, or legacy docs-expert routing.

Create mission-grounded study plans, lessons, quizzes, references, resources, and learning records. Use when the user asks to learn, study, be taught, continue a course, build a curriculum, or maintain a multi-session teaching workspace.

Plan AI-native hackathon scope, demo pitch, and judge Q&A. Use when the user needs 1-hour pitch prep, 24-hour build scoping, AI Native DevCon-style track choice, idea pressure tests, or a spec-led hack plan. Do not use for code generation, implementation support, or non-hackathon DevRel content.

Read or safely update personal TELOS, or analyze project documentation for goals, dependencies, bottlenecks, narratives, reports, and dashboards. Use for life goals, beliefs, strategies, TELOS updates, project relationship analysis, narrative points, or professional TELOS reports. Do not use for general constitutional interviews.

Binary calibration pack for recurring workflow guardrail recommendations.

Use when creating or updating a Codex skill package with focused triggers, progressive disclosure, evals, evidence, or tool integration.

Use when listing or installing Codex skills from curated sources, GitHub repo paths, private repos, or local package locations.