Agent skill

Spec Literal Execution

by ashutoshsinghpr7 in ashutoshsinghpr7/wikiskill

Apply ONLY the spec clauses literally — no aggregation, dedup, or cleanup transforms; each input record maps to its own output line.

MITAuto-check passedResearch & Science

Install Spec Literal Execution

skills CLI
$ npx skills add ashutoshsinghpr7/wikiskill --skill spec-literal-execution -a claude-code

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

GitHub CLI
$ gh skill install ashutoshsinghpr7/wikiskill spec-literal-execution --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/ashutoshsinghpr7/wikiskill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spec-literal-execution .claude/skills/spec-literal-execution && 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
spec-literal-execution
GitHub stars
268
Token cost
~385 tokens
SKILL.md length
166 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Apply ONLY the spec clauses literally — no aggregation, dedup, or cleanup transforms; each input record maps to its own output line.

  • Research & Science work in your project
  • SKILL.md covers Problem, Root cause, Fix and Evidence
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spec Literal Execution is an agent skill from ashutoshsinghpr7/wikiskill. Apply ONLY the spec clauses literally — no aggregation, dedup, or cleanup transforms; each input record maps to its own output line.

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

It sits in Research & Science. The repository describes itself as: WikiSkill (arXiv:2608.27454) for Hermes Agent — self-evolving agent skills via a persistent knowledge wiki. Faithful Algorithm 1 implementation with real agent runs, isolated… The licence is MIT.

When your agent uses it

  • Research & Science work in your project

Example prompts

  • “/spec-literal-execution”

What it can do on your machine

Read from SKILL.md and the folder at commit cdc291c. 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

Spec Literal Execution loads about 385 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 166 words of instructions outside code blocks.

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

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 ashutoshsinghpr7/wikiskill at commit cdc291c, republished under its MIT licence (© ashutoshsinghpr7). 166 words, ~385 tokens.

Download SKILL.mdSave it as .claude/skills/spec-literal-execution/SKILL.md (or your agent's skills folder).
name
spec-literal-execution
description
Apply ONLY the spec clauses literally — no aggregation, dedup, or cleanup transforms; each input record maps to its own output line.
version
1.0.0
license
MIT
platforms
linux, macos, windows

Spec Literal Execution — no unstated transforms

Problem

An exact-match grader rejected output.txt (score 0.0) although the agent believed it followed every spec clause and even re-read the file.

Root cause

Spec says "one line per product with quantity > 0" and never mentions aggregation, yet the agent inferred "product = unique product name" and summed duplicate rows (cherry 20+2 → 22, elderberry 11+6 → 17). The grader treats each JSON object as its own product row: CHERRY;20 and CHERRY;2 must be separate lines. The added transformation — not the arithmetic or tooling — caused the failure.

Fix

  • Apply ONLY the clauses literally present in the spec. Each input record maps to its own output line unless the spec explicitly says otherwise.
  • Never add aggregation, dedup, rounding, or case changes "for cleanliness".
  • If a spec filter (e.g. qty >= 10) is the only thing removing duplicates, apply it per row — do not aggregate first.

Evidence

  • FAIL: spec-format2-1 (0.0). PASS: spec-format1-1, spec-format3-1 (1.0) — same duplicate-shaped data; the passing runs filtered per row with no aggregation.

© ashutoshsinghpr7, 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/spec-literal-execution of ashutoshsinghpr7/wikiskill.

Open the folder on GitHubat commit cdc291c

Compare with similar skills

Spec Literal Execution 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.

Spec Literal Execution compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spec Literal Execution this skillashutoshsinghpr7/wikiskill268—~385Automated safety check: PassMIT
Hypothesis Generationspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Content Research Writerweapp-tailwindcss/weapp-tailwindcss1.9k25 repos~3.5kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Hypothesis Generation

    spacering-net/codeg

    Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Research & ScienceAuto-check: notes
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed
  • Content Research Writer

    weapp-tailwindcss/weapp-tailwindcss

    Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.

    1.9k GitHub starsUsed in 25 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated today
    Research & ScienceAuto-check: notes
  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

More from ashutoshsinghpr7/wikiskill

All 8 skills in this repo
  • Wikiskill Evolve

    ashutoshsinghpr7/wikiskill

    Run the WikiSkill self-evolution loop (arXiv 2608.27454) on a Hermes workspace — raw→maintainer→proposer→gate with strict Rval Rbest gating.

    268 GitHub stars~655 tokensUpdated 25 days ago
    Auto-check passed
  • Wikiskill Proposer

    ashutoshsinghpr7/wikiskill

    Propose skills from wiki patterns and traces (WikiSkill). An agent skill from ashutoshsinghpr7/wikiskill.

    268 GitHub stars~668 tokensUpdated 25 days ago
    Auto-check passed
  • Wikiskill Maintainer

    ashutoshsinghpr7/wikiskill

    Consolidate traces into the persistent wiki (WikiSkill). An agent skill from ashutoshsinghpr7/wikiskill.

    268 GitHub stars~476 tokensUpdated 25 days ago
    Auto-check passed
  • Script Exec Blocked

    ashutoshsinghpr7/wikiskill

    Sandbox approval policy blocks executecode and python3 -c; use readfile/writefile + manual transforms instead of retrying both runners.

    268 GitHub stars~281 tokensUpdated 25 days ago
    Auto-check passed
  • Search Miss Binary

    ashutoshsinghpr7/wikiskill

    ripgrep/searchfiles silently skips binary-detected files — verify empty search results with grep -a / file / xxd before concluding 'not found'.

    268 GitHub stars~327 tokensUpdated 25 days ago
    Auto-check passed
  • Trace Harness Launch Failure

    ashutoshsinghpr7/wikiskill

    Empty session traces mean launch failure, not agent behavior — verify apicallcount/toolcallcount and stdout.txt before analyzing.

    268 GitHub stars~443 tokensUpdated 25 days ago
    Auto-check passed

Questions about Spec Literal Execution

What does Spec Literal Execution do?

Apply ONLY the spec clauses literally — no aggregation, dedup, or cleanup transforms; each input record maps to its own output line. Spec Literal Execution is an agent skill from ashutoshsinghpr7/wikiskill. Apply ONLY the spec clauses literally — no aggregation, dedup, or cleanup transforms; each input record maps to its own output line.

When should I use Spec Literal Execution?

Spec Literal Execution fits situations like: research & Science work in your project.

How do I install Spec Literal Execution in Claude Code?

Run `npx skills add ashutoshsinghpr7/wikiskill --skill spec-literal-execution -a claude-code`. Or copy the skill folder (skills/spec-literal-execution in ashutoshsinghpr7/wikiskill) into .claude/skills/spec-literal-execution in your project. Claude Code loads it when a task matches its description.

How do I install Spec Literal Execution in Codex?

Run `npx skills add ashutoshsinghpr7/wikiskill --skill spec-literal-execution -a codex`. Or copy the skill folder (skills/spec-literal-execution in ashutoshsinghpr7/wikiskill) into .agents/skills/spec-literal-execution in your project. Codex loads it when a task matches its description.

Can I use Spec Literal Execution 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 ashutoshsinghpr7/wikiskill --skill spec-literal-execution -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-literal-execution, .gemini/skills/spec-literal-execution, .github/skills/spec-literal-execution and .opencode/skills/spec-literal-execution in your project.

What does Spec Literal Execution need to run?

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

Does Spec Literal Execution 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 Spec Literal Execution 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 Spec Literal Execution use?

Spec Literal Execution is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spec Literal Execution use?

About 385 tokens (SKILL.md is roughly 1.5k 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 Spec Literal Execution?

Skills that share tags, products or a category with Spec Literal Execution: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spec Literal Execution?

ashutoshsinghpr7 (a GitHub user) maintains it in ashutoshsinghpr7/wikiskill, which has 268 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 15, 2026.

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