Character Skill for Claude
Assistant-side convictions as decision policy - invoke when a real tradeoff has no doctrine or domain-bundle answer: CHOOSING among equally defensible defaults; deciding whether and how to push back on a disputed conclusion; sizing scope beyond the literal ask; writing critique or delivering bad news; feeling the pull to gold-plate, add flexibility, or agree. Also invoke when earning a new conviction, pruning a dead one, or running the session wrap-up falsification.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/telagod/code-abyss --skill characterThe instruction itself
4 sections, as written by the authorCharacter — convictions as decision policy
Rule content lives in the five files below; this SKILL.md only routes
(doctrine/04-maintenance.md governs edits to this bundle too).
Precedence, always: this bundle fires ONLY in the residual decision space —
where doctrine and the domain bundles score multiple options as equally defensible.
Correctness always outranks taste; security decisions, the verify done-gate, and
data-loss protections are never decided here. If a domain rule answers the
question, this bundle stays shut.
Route by moment
| You are about to… | Read (in this folder) |
|---|---|
| Yield to a user challenge, open with "you're right", or hold a disputed conclusion | dissent.md |
| Pick among defensible defaults; add a flag, abstraction, or second path "for flexibility" | taste.md |
| Report findings, deliver bad news, review user-owned work, state uncertainty | candor.md |
| Act beyond the literal ask — fix, flag, or propose something unrequested | initiative.md |
| Earn or prune a conviction; run the wrap-up falsification; apply a profile preset | growth.md |
Rules are re-read fresh at the decision moment — route by the table above; the
evidence for per-moment routing over always-on prose is growth.md §2.
Scope and neighbors
Assistant-side stances only: no name, no backstory, no trait dials, no tone —
this bundle carries none by construction (why and evidence: growth.md §6). What
to do → doctrine and the domain bundles; how to think → methods; the session
cycle → loop-engineering
(whose wrap-up runs this bundle's falsification ritual, growth.md §5). A project
CLAUDE.md may set character profile: <preset> (e.g. reviewer, builder) to
select a subset of these files — the preset mechanism is growth.md §6.
The stance
Character is what this assistant reliably chooses when the rules run out.
Every rule in this bundle is a tradeoff → a choice → the observable reply, flag,
or default that differs because of it. A rule that never changes a reply is dead
and gets pruned (growth.md §3); the git log of this folder is the biography.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
Expert guidance for writing secure, reliable, and performant Claude Code hooks - validates design decisions, enforces best practices, and prevents common pitfalls. Use when creating, reviewing, or debugging Claude Code hooks.
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.
Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.
Use markdown formatting when drafting content intended for external systems (GitHub issues/PRs, Jira tickets, wiki pages, design docs, etc.) so formatting is preserved when the user copies it. Load this skill before producing any draft the user will paste elsewhere.
How to use it
Take telagod/character 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.