Index of every page on this site: llms.txt
All skills
haorantang97 avatar

/polish-rule-content

@d6c47b1
by Lab 305haorantang97/labkit8 stars
Run it yourself

Revise an existing AI skill or rule for clearer discovery, useful instructions, appropriate scope, and reliable execution. Use for a requested content improvement or a demonstrated behavioral problem; a review-only request produces findings without rewriting.

  • 1 file
  • 2.7 KB
  • License
  • Updated 3 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/haorantang97/labkit/polish-rule-content

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈70 tokens for metadata: the name and description. ≈595 when used: this file.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈281 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Revise existing skill content

This is a shared module of skill-skill. Read authoring guidance for the core criteria and official validation tools. Work on the user's selected version and preserve its functioning behavior and license.

Identify the requested change. Compare the current instructions with the intended behavior and concrete failure evidence. For review or plan requests, report findings only. For an authorized edit, make the narrowest useful revision without introducing a redundant confirmation step.

Check discovery separately from execution. The description should make the capability and likely trigger clear; add exclusions only for plausible misrouting. Do not force five segments, a word-count target, negative examples or a fixed vocabulary when they add no useful distinction.

Keep the entrypoint focused on shared purpose, essential constraints and useful references. Put substantial conditional detail in supporting files when it reduces unnecessary context. Do not wait for an arbitrary line threshold, split a simple file into a routing system, or add sections merely to satisfy a template.

Use numbers and deterministic steps when the workflow has a real measurable invariant. Do not invent line limits, minimum test counts, performance targets or version claims just to make a rule look specific. Detailed gates should have a concrete reason; distinguish user conventions from host requirements and optional recommendations.

Write direct, natural instructions. Preserve the user's voice where relevant. Remove generic encouragement, repeated context, unsupported authority claims and decorative explanation. Do not globally ban ordinary words or punctuation when they express the instruction well.

Inspect callers before renaming or removing supporting files. Preserve metadata and invocation policy unless the requested change requires otherwise. Keep permissions, external actions, source boundaries and plan-only scope explicit where they materially affect the workflow.

Validate with the current official validator when available, then check changed references and behavior relevant to the edit. Use realistic input and observable outcomes for substantive behavior changes; a matching heading or phrase alone is not behavioral validation. Report what was actually verified and any remaining client test.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at d6c47b1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 3 months ago

README badge

README badge for haorantang97/labkit/polish-rule-content