agentleFS
Sign inStart free
IvanGomezMartinezIvanGomezMartinez/MatStudyLab/.agents/skills/new/SKILL.md

new

Skill2 starsChanged 3 months agoMITView on GitHub

Create a new MATLAB script and base companion in new/ after grill-me checklist.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use upgrade, gate and 3 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.
  • agenticnotetakingSkill

    upgrade

    Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

    Also in 4 projects that use this

  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 3 projects that use this

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

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

    Create a new script + base companion in new/<type>/<bundle>/ after mandatory grill-me.

    line 7
  2. Very specific:

    Read LORE.md, AGENTS.md, docs/spec.md, docs/matlab-guidelines.md, and CONTEXT.md before acting.

    line 9
  3. Very specific:

    Read and execute .agents/skills/matstudylab-bootstrap/SKILL.md before any other step.

    line 13
  4. Very specific:

    Do not proceed until bootstrap completes (skip, setup/update, or warn-and-continue).

    line 14
  5. Very specific:

    Run .agents/skills/grill-me/SKILL.md and confirm all five items:

    line 30
  6. Very specific:

    Read and apply docs/agents/matlab-skills-gate.md before writing or revising any .m file.

    line 54
  7. Distinctive:

    Default to scripts (not functions) unless reuse requires otherwise

    line 60
  8. Distinctive:

    After generation, ensure files land at:

    line 67
  9. Very specific:

    Write only under new/.

    line 96
  10. Very specific:

    Never edit codes/ in situ.

    line 97
  11. Distinctive:

    Never change units without warning.

    line 98

“Common” is measured: kept by at least 6 in 10 of the 20 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

Create a new script + base companion in new/<type>/<bundle>/ after mandatory grill-me. Write only under new/ — never edit codes/ in situ.

Read LORE.md, AGENTS.md, docs/spec.md, docs/matlab-guidelines.md, and CONTEXT.md before acting.

Step 0 — Bootstrap (mandatory)

Read and execute .agents/skills/matstudylab-bootstrap/SKILL.md before any other step. Do not proceed until bootstrap completes (skip, setup/update, or warn-and-continue). On NODE_MISSING or SYNC_FAILED_CONTINUE: warn + continue with vendored skills only — no three-option HITL menu (that menu is /build only).

Completion criterion: bootstrap outcome identified (skip, setup/update OK, or warn-and-continue).

Step 1 — Read context

AlwaysOn demand
LORE.md, AGENTS.mdRelated bundles under codes/<type>/
docs/templates/script-companion.mdSimilar scripts elsewhere in codes/

Completion criterion: equipment, units, and naming prefs from LORE are loaded.

Step 2 — Grill-me checklist (mandatory before code)

Run .agents/skills/grill-me/SKILL.md and confirm all five items:

./scripts/new-scaffold.sh checklist
  1. Optical magnitude + target codes/<type>/ folder
  2. Units / equipment
  3. Inputs, outputs, console behavior
  4. snake_case filename without verb prefix
  5. Companion .md language

Validate the filename:

./scripts/new-scaffold.sh validate <stem>

Do not generate code until grill-me passes.

Completion criterion: user confirmed all five checklist items.

Step 3 — Generate with MATLAB skills (mandatory)

Read and apply docs/agents/matlab-skills-gate.md before writing or revising any .m file.

Rules (after skills):

  • Optimal MATLAB per docs/matlab-guidelines.md; pedagogy in .md, not line comments in .m
  • %% sections only in .m; parameters in top %% Parameters block
  • Default to scripts (not functions) unless reuse requires otherwise
  • snake_case stem without verb prefix; bundle folder matches stem for 1:1 pairs

Completion criterion: script content matches the grilled requirements and MATLAB skills guidance.

Step 4 — Scaffold output paths

After generation, ensure files land at:

./scripts/new-scaffold.sh scaffold <type> <bundle> <stem>

Then replace scaffold placeholders with final script and companion content.

Output:

  • new/<type>/<bundle>/<stem>.m
  • new/<type>/<bundle>/<stem>.md

Completion criterion: both files exist under new/ with matching stems; no writes outside new/.

Step 5 — Recommend /accept

Tell the user:

/accept new

when the bundle is ready for catalog promotion.

Completion criterion: user knows how to promote the bundle.

Safety (non-negotiable)

  • Write only under new/.
  • Never edit codes/ in situ.
  • Never change units without warning; never delete measurement data.

Reference

  • Wayfinder spec: .scratch/matstudylab/issues/06-grilling-comando-new.md
  • Companion template: docs/templates/script-companion.md
  • MATLAB skills gate: docs/agents/matlab-skills-gate.md
  • Optional tools: ask-matt, research when design is unclear

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