Agent skill

Example Battery

by AHepi in AHepi/DeepReason

Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1).

MITAuto-check passed

Install Example Battery

skills CLI
$ npx skills add AHepi/DeepReason --skill example-battery -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AHepi/DeepReason example-battery --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/example-battery .claude/skills/example-battery && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
example-battery
GitHub stars
141
Token cost
~811 tokens
SKILL.md length
423 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1).

  • Works in 8 steps: Construct, as small concrete structures… → Structures are explicit and tiny: name… → Juxtapose everything in one file,… → …
  • A term needs a meaning
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • A pin is being drafted

What it does

Example Battery is an agent skill from AHepi/DeepReason. Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1). Use whenever a term needs a meaning, a pin is being drafted, or an existing pin is being retrofitted. Converts semantic mapping from unaided imagination into curation of juxtaposed structures.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The licence is MIT.

When your agent uses it

  • A term needs a meaning
  • A pin is being drafted
  • An existing pin is being retrofitted

Example prompts

  • “/example-battery”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Construct, as small concrete structures in the fragment language
  2. Structures are explicit and tiny: name the sorts, list the elements,
  3. Juxtapose everything in one file, positives beside their near-miss
  4. If the term has a recorded risk corridor ("too weak admits X, too
  5. If you cannot construct three positives, the term is not understood
  6. Battery instances carry ids. Digests are produced ONLY by the repo's
  7. The battery file is parsed by machines: its exact grammar (heading
  8. Instances are proto-members of the model zoo and feed the denotation

What it can do on your machine

Read from SKILL.md and the folder at commit 9607fba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Example Battery loads about 811 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 423 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~811

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AHepi/DeepReason at commit 9607fba, republished under its MIT licence (© AHepi). 423 words, ~811 tokens.

Download SKILL.mdSave it as .claude/skills/example-battery/SKILL.md (or your agent's skills folder).
name
example-battery
description
Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1). Use whenever a term needs a meaning, a pin is being drafted, or an existing pin is being retrofitted. Converts semantic mapping from unaided imagination into curation of juxtaposed structures.

Example Battery (Reed 1)

<!-- PROMPT-CORE-BEGIN -->

Before any clause about a term's meaning is written, build its battery.

  1. Construct, as small concrete structures in the fragment language:
    • =3 POSITIVE instances the intended meaning must admit;

    • =3 NEAR-MISS negatives, each a minimal pair with a positive - identical except in one respect, which the meaning must exclude;

    • =1 BOUNDARY case whose classification is genuinely undecided, recorded as OPEN with the question stated.

  2. Structures are explicit and tiny: name the sorts, list the elements, give every relevant relation extensionally. No instance is described only in prose.
  3. Juxtapose everything in one file, positives beside their near-miss partners, with one line per pair naming the single difference. Near-misses are pairwise DISTINCT in the clause that admits them: no two N-instances may be the same single-bit flip of (structurally) the same positive -- a battery's discriminating power is the count of distinct negative shapes, not the count of N labels. Any structural assumption not present in the inventory candidate (e.g. licensing a chained/transitive reading of a relation) is never a silent positive: it becomes a boundary (B) instance carrying the question, or it is omitted.
  4. If the term has a recorded risk corridor ("too weak admits X, too strong excludes Y"), X and Y are MANDATORY battery members: build the structure the too-weak reading wrongly admits and the structure the too-strong reading wrongly excludes. A corridor without its two walls built is not yet analyzed.
  5. If you cannot construct three positives, the term is not understood well enough to pin: record what blocks each attempted instance and stop. That record is the deliverable.
  6. Battery instances carry ids. Digests are produced ONLY by the repo's digest tool (scripts/battery_digest.py --write) over the canonical instance bytes; NEVER compute, estimate, or invent a digest yourself. Write the literal placeholder PENDING-DIGEST in every digest cell and let the acceptance command run the tool. A hand-written hash is a fabrication even if it happens to be correct.
  7. The battery file is parsed by machines: its exact grammar (heading form, id pattern, registry table columns) is defined in zoo/batteries/FORMAT.md and is provided to you as a READ-ONLY REFERENCE section in your context. Conform to it byte-exactly. If that reference section is absent or marked MISSING, STOP and report BLOCKED requesting it -- never invent structure; semantically fine but mechanically unparseable output is a failure.
  8. Instances are proto-members of the model zoo and feed the denotation tests. Never delete a battery instance a pin fails on; a failed instance is evidence, not clutter.
Show full SKILL.md (1 more words)Show less
<!-- PROMPT-CORE-END -->

© AHepi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/example-battery of AHepi/DeepReason.

Open the folder on GitHubat commit 9607fba

Compare with similar skills

Example Battery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Example Battery compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Example Battery this skillAHepi/DeepReason141—~811Automated safety check: PassMIT
Arize Evaluatorgithub/awesome-copilot40k2 repos~8.1kAutomated safety check: NotesMIT
LLM Evaluationdavila7/claude-code-templates32k13 repos~3.5kAutomated safety check: PassMIT
Agent Evaluationsickn33/agentic-awesome-skills47k1 repos~2kAutomated safety check: PassMIT
Instance Awarenessn8n-io/n8n207k—~1.4kAutomated safety check: PassCustom licence
EvaluatorsArize-ai/phoenix12k—~1.7kAutomated safety check: PassCustom licence

Similar skills

  • Arize Evaluator

    github/awesome-copilot

    Official

    Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…

    40k GitHub starsUsed in 2 repos~8.1k tokens
    AI & LLM EngineeringAuto-check: notes
  • LLM Evaluation

    davila7/claude-code-templates

    Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.

    32k GitHub starsUsed in 13 repos~3.5k tokens
    AI & LLM EngineeringAuto-check passed
  • Agent Evaluation

    sickn33/agentic-awesome-skills

    Evaluate agent behavior with versioned cases and explicit verifiers.

    47k GitHub starsUsed in 1 repo~2k tokens
    Agent WorkflowsAuto-check passed
  • Official

    Load when the request depends on what is already on this instance rather than on what the user just typed: a short or ambiguous opener ("fix it", "carry on", "what should I look at"), a reference to…

    207k GitHub stars~1.4k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Evaluators

    Arize-ai/phoenix

    Author or refine a Phoenix evaluator — code or LLM-as-a-judge — that scores a run's output.

    12k GitHub stars~1.7k tokensUpdated today
    EducationAuto-check passed
  • Agent Evaluation Reporting

    sickn33/agentic-awesome-skills

    A skill your agent uses when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.

    47k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

More from AHepi/DeepReason

All 30 skills in this repo
  • Pinker Clarity Workflow

    AHepi/DeepReason

    Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both.

    141 GitHub stars~1.5k tokensUpdated 27 days ago
    Auto-check passed
  • Design, deliver, or audit explanations and lessons with a Pinker-informed focus on phenomena, the curse of knowledge, concrete models, active reasoning, feedback, and revision.

    141 GitHub stars~1.8k tokensUpdated 27 days ago
    Auto-check passed
  • Pinker Write For Readers

    AHepi/DeepReason

    Draft, revise, teach, or audit expository prose using Pinker's cognitive approach to style: classic presentation, reader modeling, curse-of-knowledge repair, coherent information order, deliberate…

    141 GitHub stars~2.1k tokensUpdated 27 days ago
    Auto-check passed
  • Authoring Skills

    AHepi/DeepReason

    Rules for writing, editing, and retiring skill and workflow files for LLM agents.

    141 GitHub stars~1.7k tokensUpdated 27 days ago
    Auto-check passed
  • Deepreason Orchestrator

    AHepi/DeepReason

    Entry point for any DeepReason problem. An agent skill from AHepi/DeepReason.

    141 GitHub stars~1.1k tokensUpdated 27 days ago
    Auto-check passed
  • Dr Audit Orchestrator

    AHepi/DeepReason

    Router for the code-audit family. An agent skill from AHepi/DeepReason.

    141 GitHub stars~1.1k tokensUpdated 27 days ago
    Auto-check passed

Questions about Example Battery

What does Example Battery do?

Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1). Example Battery is an agent skill from AHepi/DeepReason. Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1).

When should I use Example Battery?

Example Battery fits situations like: A term needs a meaning; A pin is being drafted; an existing pin is being retrofitted.

How do I install Example Battery in Claude Code?

Run `npx skills add AHepi/DeepReason --skill example-battery -a claude-code`. Or copy the skill folder (skills/example-battery in AHepi/DeepReason) into .claude/skills/example-battery in your project. Claude Code loads it when a task matches its description.

How do I install Example Battery in Codex?

Run `npx skills add AHepi/DeepReason --skill example-battery -a codex`. Or copy the skill folder (skills/example-battery in AHepi/DeepReason) into .agents/skills/example-battery in your project. Codex loads it when a task matches its description.

Can I use Example Battery in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AHepi/DeepReason --skill example-battery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/example-battery, .gemini/skills/example-battery, .github/skills/example-battery and .opencode/skills/example-battery in your project.

What does Example Battery need to run?

SKILL.md names no scripts, command-line tools or credentials: Example Battery is instructions for the agent only.

Does Example Battery access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Example Battery safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Example Battery use?

Example Battery is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Example Battery use?

About 811 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Example Battery?

Skills that share tags, products or a category with Example Battery: Arize Evaluator (github/awesome-copilot, 40k stars), LLM Evaluation (davila7/claude-code-templates, 32k stars), Agent Evaluation (sickn33/agentic-awesome-skills, 47k stars) and Instance Awareness (n8n-io/n8n, 207k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Example Battery?

AHepi (a GitHub user) maintains it in AHepi/DeepReason, which has 141 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on September 10, 2026.

Source: AHepi/DeepReason on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.