agentleFS
Sign inStart free
sb-devsb-dev/narrative-production-skills/.claude/skills/skill-optimizer/SKILL.md

skill-optimizer

Skill2 starsChanged 3 months agoMITView on GitHub

Optimizes AI skills for activation, clarity, and cross-model reliability. Use when creating or editing skill packs, diagnosing weak skill uptake, reducing regressions, tuning instruction salience, improving examples, shrinking context cost, or setting benchmark/release gates for skills. Trigger terms: skill optimization, activation gap, benchmark skill, with/without skill delta, regression, context budget, prompt salience.

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use octocat, linting-neostandard-eslint9 and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mcollinaSkill

    octocat

    Use this skill whenever the prompt contains any `github.com` URL, even if the user only pastes a link and gives no GitHub-specific keywords. Handles git and GitHub operations using the gh CLI. Triggers include any GitHub link to an issue, pull request, commit, compare page, Actions run, release, discussion, or repository. Covers creating and reviewing PRs, repository security advisories (GHSA), their comments, and fix PRs in their temporary private forks, private vulnerability report discussions, watching CI checks, interactive rebasing, branch cleanup, submodule management, and repository archaeology with git log/blame/bisect.

    Also in 3 projects that use this

  • mcollinaSkill

    linting-neostandard-eslint9

    Configures ESLint v9 flat config and neostandard for JavaScript and TypeScript projects, including migrating from legacy `.eslintrc*` files or the `standard` package. Use when you need to set up or fix linting with `eslint.config.js` or `eslint.config.mjs`, troubleshoot lint errors, configure neostandard rules, migrate from `.eslintrc` to flat config, or integrate linting into CI pipelines and pre-commit hooks.

    Also in 3 projects that use this

  • VercelSkill

    oauth

    Configure OAuth providers (Google, Apple, Microsoft, Facebook, GitHub, etc.) to work with portless local dev URLs. Use when setting up OAuth redirect URIs, fixing "redirect_uri_mismatch" or "invalid redirect" errors, configuring sign-in providers for local development, or when a provider rejects .localhost subdomains. Triggers include "OAuth not working with portless", "redirect URI mismatch", "Google/Apple/Microsoft sign-in fails locally", "configure OAuth for local dev", or any task involving OAuth callback URLs with portless domains.

    Also in 3 projects that use this

  • AnthropicSkill

    documentation

    Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

    Also in 3 projects that use this

  • MicrosoftSkill

    init

    Also in 3 projects that use this

  • +2 more from mcollina

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when you need to:

    line 10
  2. Distinctive:

    add concrete integrated examples

    line 26
  3. Distinctive:

    Read individual rule files for detailed procedures and templates:

    line 33
  4. Distinctive:

    Prefer few high-signal rules over many soft recommendations

    line 43
  5. Distinctive:

    Put fragile, high-value behaviors in top-level checklists

    line 44
  6. Distinctive:

    Add explicit wording for what must not be omitted

    line 46

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to use

Use this skill when you need to:

  • Improve whether a skill is actually applied by models
  • Diagnose why some criteria fail across all models
  • Prevent a skill from making outputs worse
  • Refactor skill text for stronger retrieval under context pressure
  • Build repeatable benchmark loops and release gates

Optimization loop (default workflow)

  1. Measure baseline and skill-on behavior (per model, per scenario, per criterion)
  2. Find failure pattern:
    • universal failure (0% with skill)
    • model-specific weakness
    • regression (negative delta)
  3. Edit for salience:
    • add explicit triggers
    • add concrete integrated examples
    • tighten checklists and decision rules
  4. Re-run evals and compare deltas
  5. Ship with guardrails (documented gate + run history + follow-up issues)

How to use

Read individual rule files for detailed procedures and templates:

  • rules/benchmark-loop.md - End-to-end benchmark loop and scoring
  • rules/activation-design.md - Improve retrieval and instruction uptake
  • rules/context-budget.md - Reduce token cost without losing behavior
  • rules/regression-triage.md - Diagnose and fix skill-on regressions
  • rules/release-gates.md - Go/no-go criteria before shipping skill updates

Practical heuristics

  • Prefer few high-signal rules over many soft recommendations
  • Put fragile, high-value behaviors in top-level checklists
  • Include at least one integrated example per common scenario
  • Add explicit wording for what must not be omitted
  • Track gains/losses with with-skill vs without-skill comparisons

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free