agentleFS
skforecastskforecast/skforecast-ai/.claude/skills/sync-skforecast-assets/SKILL.md

sync-skforecast-assets

Skill52 starsChanged 47 days agoApache-2.0View on GitHub

Sync the skills and llms-base.txt from the skforecast repository and update the files maintained by hand when the skill inventory changes.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run PY tools/ai/sync_skforecast_assets.py (add --branch $ARGUMENTS when an argument was given).

    line 16
  2. Very specific:

    Read the report: skills added, removed, renamed or with a new description, and the token estimates the script rewrote in …

    line 18
  3. Distinctive:

    Update the files maintained by hand:

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Sync skforecast assets

skforecast_ai/skills/ and skforecast_ai/resources/llms-base.txt are denied for Edit and Write; they change only through this script. It needs network access to GitHub.

  1. git status --short must show no changes under skforecast_ai/skills/ or skforecast_ai/resources/.
  2. Run PY tools/ai/sync_skforecast_assets.py (add --branch $ARGUMENTS when an argument was given). PY as in /verify.
  3. Read the report: skills added, removed, renamed or with a new description, and the token estimates the script rewrote in skforecast_ai/llm/skills.py. If the inventory did not change, go to step 5.
  4. Update the files maintained by hand:
    • skforecast_ai/llm/skills.py: ALL_SKILLS and the routing tables.
    • The table in docs/user-guides/skills.md (tests/test_docs_skills_page.py checks it against ALL_SKILLS).
    • The upstream order test in tests/tests_llm/test_select_skills.py.
  5. PY tools/ai/measure_skill_tokens.py --check, then /verify.
  6. Skills are part of what ask() sends to the model: remind the user that a real-model check_ask_context.py run is due before the release (see /llm-context-change).

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.