agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/design-training/SKILL.md

design-training

Skill4 starsChanged 6 days agoMITView on GitHub

Designs a capacity-development program: needs assessment, curriculum, labs, assessment and ownership-transfer plan.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.

    line 26
  2. Very specific:

    Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …

    line 28
  3. Distinctive:

    Use lego sets to teach model structure by assembling and swapping bricks

    line 48
  4. Distinctive:

    After the needs assessment

    line 53
  5. Distinctive:

    After the curriculum outline

    line 54
  6. Distinctive:

    No follow-up after workshops

    line 59

≈ “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
<!-- Generated from .claude/skills/design-training/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/design-training — Design Training

Category: Capacity Development · Primary agent: training-curriculum-designer

Designs a capacity-development program: needs assessment, curriculum, labs, assessment and ownership-transfer plan.

Arguments: whatever the user wrote after the command name.

Purpose

Design a capacity-development program that leaves counterparts able to run, maintain and extend a model on their own: needs assessment, a progressive curriculum by model class, labs with open or synthetic data, assessments, and a clear criterion for transferring model ownership, followed by mentoring. The output is a program measured by what participants can do, not by attendance.

Use it when a model is handed over, a counterpart institution builds modeling capacity, or a team adopts a new model class.

Do not use it when a single exercise is enough (/create-exercise).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Counterpart description
    • Model to be transferred If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
  2. Check confidentiality. Identify the data classification level of the inputs (.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
  3. Collaboration. Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.

Agents

  • training-curriculum-designer — primary agent; coordinates the work and integrates results
  • technical-documentation-specialist — Writes technical documentation
  • stakeholder-liaison-specialist — Interfaces with stakeholders and counterparts

Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.

Key design decisions (present options, let the user choose)

DecisionTypical optionsWhat it changes
Levelintroductory, intermediate, advancedCurriculum
Model classesgap models, FPAS, DSGE, CGE, econometrics, MLContent
Deliveryworkshops, blended, embedded mentoringRetention
Ownership criterionindependent forecast round, model modification, validationSuccess measure

Workflow

  1. Assess counterpart skills, tools, data access and goals
  2. Design a progressive curriculum by model class; create labs with open or synthetic data
    • Use lego sets to teach model structure by assembling and swapping bricks
  3. Define assessments and the criterion for model ownership transfer
  4. Draft follow-up mentoring schedule

Checkpoints with the user

  • After the needs assessment
  • After the curriculum outline

Common pitfalls

  • Lecture-heavy delivery
  • Labs that depend on confidential data
  • No follow-up after workshops

Output

docs/training/<program>/

The program folder holds the needs assessment, curriculum, labs, assessments, ownership criterion and mentoring schedule.

Gate / verdict

  • Training data are non-confidential or synthetic; ownership-transfer criterion defined
  • Assessments are practical tasks

Suggested next steps

  • /create-exercise

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.