Skip to content
cccskills
FreePublished on GitHub

prompt-token-efficiency

Rewrite long prompts into shorter, clearer instructions for language models. Preserve essential requirements while removing repetition, defining scope, and making output formats and success criteria explicit to reduce ambiguity and unnecessary tokens.

OriginalShow the original description

Rewrite prompts for minimal tokens, maximal clarity, and low ambiguity for LLM consumption.

See how to install

Good for

  • Shortening a long prompt while preserving requirements
  • Clarifying vague instructions and success criteria
  • Making output formats and length limits explicit
  • Removing repeated or conflicting instructions

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Prompt Token Efficiency

Use this skill to compress prompts while preserving intent and output quality.

Goals

  1. Minimize token count
  2. Maximize clarity
  3. Minimize ambiguity
  4. 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:

  1. Start with the objective in one short sentence.
  2. Keep only facts needed to complete the task.
  3. Replace long qualifiers with concrete limits.
  4. Remove filler words that do not change behavior.
  5. 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw5.4KUpdated Oct 19, 2026

agent-conduct

FreeSummary

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw5.4KUpdated Oct 19, 2026

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw5.4KUpdated Oct 19, 2026

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw5.4KUpdated Oct 19, 2026

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw5.4KUpdated Oct 19, 2026

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw5.4KUpdated Oct 19, 2026

See all skills by github

Report a problem with this skill