Methods

Skill telagod/code-abyss/skills/_kernel/methods

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.From its SKILL.md

Install

npx -y skills add telagod/code-abyss --skill methods

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

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.

What ships with it: 5 files

20.8 KB alongside SKILL.md

Gives 0 of the 12 instructions most docs writing skills give in 383 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

Use third-person for skill descriptionsin 54 of 1951, across 35 files
Start descriptions with Use whenin 43 of 1951, across 29 files
Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
Use active voicein 40 of 1951, across 36 files
Map file responsibilities before defining tasksin 36 of 1951, across 29 files
Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
Ask one question at a timein 35 of 1951
Offer execution options after saving the planin 33 of 1951, across 24 files
Include complete code in every stepin 33 of 1951, across 27 files
Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
Announce the skill usage at the startin 30 of 1951
Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

Read the file matching the current task
Consult doctrine before methods
Label beliefs 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.