The operating doctrine, self-contained in this folder. Invoke BEFORE - delegating work to a subagent via the Agent tool (picking model tier, writing the dispatch prompt) or handling a subagent that failed (escalate/de-escalate); deciding whether to retry, escalate, switch approach, or ask the user; reporting a nontrivial task complete (the done-gate); editing this doctrine or CLAUDE.md; recording a lesson about the harness.
npx skills add https://github.com/telagod/code-abyss --skill doctrine
All referenced files live in this skill's folder; read them with relative paths from here.
The three always-on laws live in the user's ~/.claude/CLAUDE.md router; this bundle carries
the depth. Content lives in the numbered files — this SKILL.md only routes; never duplicate
rule text into it.
| Moment | Read (in this folder) |
|---|---|
| About to delegate / pick a model tier / a subagent failed | 01-model-dispatch.md, then fill a template from 03-delegation-templates.md |
| Retry? escalate? done? ask the user? direction feels wrong? | 02-judgment.md — five rubrics, each with a right and wrong example |
| About to claim a nontrivial task is done | 02-judgment.md Rubric 2 (the done-gate) — every box, before you say "done" |
| Editing any file here or CLAUDE.md; recording a lesson | 04-maintenance.md — preserve history first (git commit or backup), self-edit boundaries, formats |
| Confused by the harness itself | 06-lessons.md first (it may already be paid for), then 00-diagnosis.md |
| First session in a new environment, or sharing this bundle | INSTALL.md |
| Why these rules exist; environment-specific warnings | 00-diagnosis.md, 05-letter.md |
01).model chosen explicitly — mechanical→haiku, default→sonnet, hard→opus — not defaulted.Would raw output ≫ the answer? → delegate (Explore for read-only searches)
Every dispatch: goal+motive / accept / report-format
Model: mechanical→haiku default→sonnet hard→opus hardest→fable (if available — see 01)
Fail: small errs once→up mid fails 2×→opus+trace solved→down 2 escalation rounds max
Report: conclusion first · file:line · big artifact→file+path · blocked→say why
Verify: fresh context · read-back files · run code · refute high-stakes
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.
Convert abstract edge concepts into strategy draft variants and optional exportable ticket YAMLs for edge-candidate-agent export/validation.
INVOKE THIS SKILL when writing ANY LangGraph code. Covers StateGraph, state schemas, nodes, edges, Command, Send, invoke, streaming, and error handling.
Analyze the protocol layer between agent harness and LLM model. Use when (1) understanding message wire formats and API contracts, (2) examining tool call encoding/decoding mechanisms, (3) evaluating streaming protocols and partial response handling, (4) identifying agentic chat primitives (system prompts, scratchpads, interrupts), (5) comparing multi-provider abstraction strategies, or (6) understanding how frameworks translate between native LLM APIs and internal representations.
Translate SKILL.md and README.md files into multiple languages for sharing skills internationally
| Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared skills, `.agents/config.json`, generated shim behavior, provider discovery paths, or install-time agent sync.
>- Summarizes Google Cloud Data Lineage graphs to help users debug data quality issues and understand data provenance for BQ/GCS. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).
Take telagod/doctrine from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.