Methods
Give your AI coding agent a personality. Composable persona + style + skills for Claude Code, Codex, Gemini CLI & OpenClaw. Ships Tech Persona Card v1.0 spec.
npx -y skills add telagod/code-abyss --skill methodsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
How to think through work, distilled from a stronger model's demonstrated moves - invoke when STARTING to investigate a confusing behavior or debug a root cause; design or evaluate an approach/proposal; plan a multi-step or long-running task; verify work, review findings, or reconcile conflicting reports; write rules, reports, or docs someone else must act on.
SKILL.md
2.0 KB, 383 tokens by cl100k_base, as published. Nobody here has run it
Methods — how to think, by moment
Five domains, each distilled from moves a stronger model actually made (the examples cite
real founding-session events; most are verifiable in the repo — git log, the doctrine
files, archive/ — and the rest come from the founding session's own recorded account).
Governance — whether to delegate, escalate, stop, or claim done — lives in the doctrine
skill; this bundle is how to work the problem once you're in it.
Route by moment
| You are about to… | Read (in this folder) |
|---|---|
| Investigate a bug, a confusing behavior, an unfamiliar system, an anomaly | investigate.md |
| Propose, design, or evaluate an approach (incl. someone else's suggestion) | design.md |
| Start a task with more than ~3 steps, or one that could be interrupted | execute.md |
| Check work — yours or a reviewer's; weigh conflicting reports | verify.md |
| Write anything another model or person must act on (rules, reports, docs) | communicate.md |
Read the ONE file that matches; each is self-contained. If two match (e.g. designing a
verification), read both — they're short. When a task fires this bundle AND doctrine (e.g. "review
this PR" is both a delegation decision and a verification method): doctrine FIRST — decide
whether and to whom to delegate — then the matching methods file for how to do the work.
The stance that generates all five
Every belief is either verified this session or hearsay — the labeling discipline
and the rest of the stance live in investigate.md §3, which is their single home.
Gives 0 of the 12 instructions most docs writing skills give in 383 tokens
Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-06
- announce the skill at startin 54 of 1637, across 21 files
- convert legacy doc files before editingin 45 of 1637, across 7 files
- predict questions readers might askin 42 of 1637, across 3 files
- Generate clarifying questions for initial contextin 42 of 1637, across 3 files
- Create document scaffold with placeholder textin 42 of 1637, across 3 files
- Brainstorm content options for each sectionin 42 of 1637, across 3 files
- Test document with fresh context-less instancein 42 of 1637, across 3 files
- ask interview questions one at a timein 42 of 1637, across 26 files
- include exact file paths in every taskin 42 of 1637, across 15 files
- Apply surgical edits during refinementin 41 of 1637, across 2 files
- Offer structured workflow or freeformin 40 of 1637, across 1 file
- Ask for document meta-contextin 40 of 1637, across 1 file
Said here and by no other author read
- read the single file matching your task
- consult doctrine before this skill
- decide delegation using the doctrine skill
- label every belief as verified or hearsay
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.