House skills

How tikoci repositories are developed and maintained, written as agent-agnostic SKILL.md files. They are defaults, not mandates: a repository copies the skills it uses into .agents/skills/, lists them in its AGENTS.md, and records any exception there. Start with tikoci-house.

Each skill directory is published unchanged under https://tikoci.dev/house/skills/<name>/. index.json lists every skill with its files for scripted copies; skills/README.md describes the layout and checks. Source and history: tikoci/tikoci.github.io, planning in issue #21.

Skills

tikoci-grounding

Ground claims in the real system: RouterOS on a CHR booted by quickchr decides RouterOS behavior, not docs, memory or review; run the call before changing code. One failure is a lead: reproduce it locally before naming a cause, and never skip, gate, retry or raise a timeout to turn red green. Unproven causes stay out of docs, issues and skills. Done means the exercising test ran, checks not run are reported and the CI step is named. Use when debugging, measuring or claiming done.

Also: references/sources.md

tikoci-home

Where tikoci tools keep files: the user scope TIKOCI_HOME (default ~/.tikoci, %LOCALAPPDATA%\tikoci on Windows, no XDG) and a project's .tikoci/, the nearest one above the working directory and below home. Each tool owns TOOL/ in each scope; other tools use it through its library or CLI, never its files. tikoci does not define the directory around .tikoci/ or how it is shared. .tikoci/TOOL/ travels (no secrets, allowlisted settings); .tikoci/TOOL/local/ never does, is read only when private and trusted at the CLI, and a git worktree uses its main checkout's. Cache in TIKOCI_CACHE_DIR, runtime in run/TOOL/, port claims in the host scope. TIKOCI_SANDBOX replaces the user scope for tests: no project, legacy path or keychain, no eviction of the shared cache. Names across scopes: name, user:name, label:name. Repos adopt it in profiles. Use when adding a file a tool keeps outside the checkout, an env override, a settings layer, a cache, a cross-tool reference or a test that touches user state.

Also: references/conformance.json, references/isolation.md, references/layout.md, references/layout.tsv, references/settings.md, references/sources.md, scripts/tikoci-paths.ts

tikoci-house

How a tikoci repo sets up agent instructions and skills. AGENTS.md is the one entry file and CLAUDE.md is the single line @AGENTS.md; add no new .github/instructions files. Repo skills live in .agents/skills (.claude/skills links to it); house tikoci-* skills from tikoci.dev/house/skills are copied unchanged or referenced by URL, listed in AGENTS.md, and any deviation is noted once under House exceptions. Precedence: the maintainer's explicit instruction, then the nearest AGENTS.md, then house skills, then user-level notes. Temporary work goes in a gitignored .scratch/. Machine facts (paths, hosts, accounts, harnesses) stay in the operator's local agent notes, never in a repo or skill. Use when creating or editing AGENTS.md, CLAUDE.md, .agents/ or a SKILL.md, adopting a house skill, or deciding where a rule belongs.

Also: references/sources.md, references/writing-house-skills.md

tikoci-testing

How tikoci repos test: bun:test; unit tier on every PR, smoke integration on a real CHR via quickchr behind an env flag, a channel sweep nightly and before release, lab work outside CI. Every behavior change ships a test that can fail: assert what the code decides and output markers, not exit 0. Hermetic: TIKOCI_SANDBOX, explicit child env, port 0, cleanup in finally, timeouts from the operation's budget. Use when writing tests, mocks or test tiers.

Also: references/patterns.md, references/sources.md

4 skills; descriptions use 2766 of 8000 characters.