generate-asset-actions
Skill747 starsChanged 36 days agoMITView on GitHub
Generate asset-actions.yaml from ASSETS.yaml by classifying assets into priority tiers. Use when the user asks to regenerate, update, or refresh the asset actions.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-repo-contextSkill
- check-trajectories-workflowSkill
- ci-maintenance-workflowSkill
- code-quality-fix-allSkill
- code-quality-review-allSkill
- create-evalSkill
- ensure-test-coverageSkill
- eval-quality-workflowSkill
- eval-report-workflowSkill
- eval-validity-reviewSkill
- investigate-datasetSkill
- prepare-releaseSkill
- prepare-submission-workflowSkill
- read-eval-logsSkill
- security-audit-evalSkill
- verify-scoring-changeSkill
- write-an-adrSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
If ASSETS.yaml may be stale, run uv run python tools/generate_asset_manifest.py first.
- Very specific: line 12
Run uv run python tools/summarise_asset_manifest.py to get aggregate counts (by type, by state, totals).
- Very specific: line 16
Read ASSETS.yaml. For each asset, determine target stage first, then priority.
- Very specific: line 37
Every entry needs: eval, source, type, state, target, action, reason.
- Distinctive: line 41
Update this list when new instability is discovered.
- Very specific: line 59
Every floating asset in ASSETS.yaml appears in urgent, high, or medium
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Generate Asset Policy
Regenerate internal/audits/asset-actions.yaml and internal/audits/audit-summary.md from ASSETS.yaml.
If ASSETS.yaml may be stale, run uv run python tools/generate_asset_manifest.py first.
Run uv run python tools/summarise_asset_manifest.py to get aggregate counts (by type, by state, totals). Use these numbers when populating audit-summary.md.
Classification
Read ASSETS.yaml. For each asset, determine target stage first, then priority. Process both state: floating assets AND state: pinned assets that match known-unstable sources (since their target is controlled, they are not yet at their target stage).
Target stages (per ADR-0007)
The target stage depends on host reliability, not asset type:
controlled(Stage 2) — any asset where upstream has broken before, maintainer is unresponsive/deprecated, OR host is unreliable (personal repos, Google Drive,.edudomains, university servers, any host without version control). This applies togit_clone,direct_url, andhuggingfacealike.pinned(Stage 1) — assets on reliable, version-controlled hosts (GitHub, HuggingFace, well-known CDNs) with no history of breakage.
Per ADR-0007: "Anything hosted on a less reliable domain (personal websites, Google Drive, university servers, or any host without version control) should skip straight to Stage 2."
Priority tiers
- Urgent — all other floating refs on reliable hosts. Target is
pinned. - High — matches a known-unstable source (see registry below). Target is
controlled. - Medium — unreliable host (
drive.google.com,.edudomains, personal repos/websites) not already in the known-unstable registry. Target iscontrolled.
For assets with state: pinned and a {SHA} placeholder but no checksum, classify as Low (target: pinned with checksum).
Omit assets already at their target stage.
Every entry needs: eval, source, type, state, target, action, reason.
Known-Unstable Sources
Update this list when new instability is discovered.
| Source | Eval | Incident |
xlang-ai/OSWorld | osworld | Files removed (PR #958) |
openai/evals | makemesay | Deprecated upstream |
corebench.cs.princeton.edu | core_bench | University server, no versioning |
epatey/fonts | osworld | Personal repo |
ShishirPatil/gorilla | bfcl | Data format issues (PR #954) |
yunx-z/MLRC-Bench | mlrc_bench | Broken task |
LRudL/sad | sad | Upstream bugs (issues #7, #8) |
meg-tong/sycophancy-eval | sycophancy | Invalid JSON/NaN, workaround in code |
josancamon/paperbench | paperbench | Paper ID mismatch (HF discussion #2) |
sentientfutures/moru-benchmark | moru | Exact duplicate rows |
Verification
asset-actions.yamlparses as valid YAML- Every floating asset in ASSETS.yaml appears in urgent, high, or medium
floating_assets + needing_checksums + no_action_needed == total_external_assets- Numbers in
audit-summary.mdmatch output ofsummarise_asset_manifest.py
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
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.

