494 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4864
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
npx skills add https://github.com/github/gh-aw --skill prompt-token-efficiency
The instruction itself
7 sections, as written by the author
Prompt Token Efficiency
Use this skill to compress prompts while preserving intent and output quality.
Goals
- Minimize token count
- Maximize clarity
- Minimize ambiguity
- Optimize for LLM execution, not human prose style
Core Rules
- Keep only task-critical information.
- Remove pleasantries, repetition, and narrative framing.
- Prefer short, concrete instructions over descriptive paragraphs.
- Use explicit constraints and output format requirements.
- Use stable terminology (one term per concept).
- Replace vague words (
appropriate, some, better) with measurable criteria.
- Put required context before optional context.
- Avoid conflicting instructions.
Prose Compression Pattern
Rewrite prose to be direct and compact:
- Start with the objective in one short sentence.
- Keep only facts needed to complete the task.
- Replace long qualifiers with concrete limits.
- Remove filler words that do not change behavior.
- End with explicit success criteria.
LLM-Optimized Writing Style
- Use imperative statements.
- Prefer bullets over long prose.
- Keep each instruction atomic.
- Avoid examples unless needed to prevent failure.
- If examples are required, include one minimal example.
Ambiguity Checks
Before finalizing a prompt, verify:
- Any undefined noun is resolved.
- Any pronoun has a clear antecedent.
- Scope limits are explicit (time range, file range, quantity limits).
- Success criteria are testable.
- Output format is unambiguous.
Prose Rewrite Checks
When rewriting, ensure the final prompt:
- Uses fewer words than the original.
- Preserves all required constraints.
- Uses concrete nouns instead of pronouns where possible.
- Avoids optional wording unless options are actually allowed.
- States required output and any length bound in plain language.