agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/build-llm-pipeline/SKILL.md

build-llm-pipeline

Skill4 starsChanged 6 days agoMITView on GitHub

Builds an LLM pipeline for extraction, classification or analysis with verification, evaluation and confidentiality controls.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Create a labelled evaluation set before building prompts

    line 49
  4. Distinctive:

    Document failure modes, human review requirements and monitoring

    line 54
  5. Distinctive:

    After the confidentiality check: confirm the endpoint

    line 58
  6. Distinctive:

    After the evaluation set: confirm thresholds

    line 59
  7. Distinctive:

    After evaluation: approve release and review level

    line 60
  8. Distinctive:

    Every extracted number is traceable to its source

    line 77

≈ “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/build-llm-pipeline/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/build-llm-pipeline — Build LLM Pipeline

Category: Build (AI) · Primary agent: llm-economic-analyst

Builds an LLM pipeline for extraction, classification or analysis with verification, evaluation and confidentiality controls.

Arguments: whatever the user wrote after the command name.

Purpose

Build an LLM pipeline for extraction, classification or analysis of economic documents that is evaluated like a measurement instrument: confidentiality cleared first, a labelled evaluation set built before prompts, structured outputs verified against sources, and accuracy measured against agreed thresholds. The output is a pipeline with an evaluation card and defined human review.

Use it when large document collections must be read for numbers, measures, stances or facts, or text must be classified at scale.

Do not use it when questions are answered from a document collection with citations (/build-rag-kb), or the task is to simulate agents (/build-llm-agents).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Task definition
    • Labelled evaluation sample 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

  • llm-economic-analyst — primary agent; coordinates the work and integrates results
  • nlp-text-as-data-specialist — Turns text into economic data
  • llm-red-team-specialist — Red-teams LLM systems
  • data-governance-metadata-specialist — Owns data governance and metadata

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
Model and endpointinternal, approved external, localConfidentiality and quality
Output formatJSON schema, labels, short textVerifiability
Verificationsource quotation, cross-check with databases, consistency rerunsError detection
Thresholdsaccuracy and numeric faithfulness targetsRelease decision
Human reviewfull, sampled, exceptions onlyCost and risk

Workflow

  1. Classify input data by confidentiality; confirm the allowed model/endpoint before any prompt is written
  2. Create a labelled evaluation set before building prompts
    • Cover document types, languages and hard cases; keep a held-out portion
  3. Design structured-output prompts and verification steps (source cross-check, schema validation)
  4. Evaluate accuracy, numeric faithfulness and stability across prompt/model versions
    • Error analysis by field and document type
  5. Document failure modes, human review requirements and monitoring
    • Freeze prompt versions; rerun evaluation after any model change

Checkpoints with the user

  • After the confidentiality check: confirm the endpoint
  • After the evaluation set: confirm thresholds
  • After evaluation: approve release and review level

Common pitfalls

  • Prompts tuned on the evaluation set
  • Fluent outputs accepted without source checks
  • Silent model-version changes
  • Confidential documents sent to unapproved services

Output

models/llm/<name>/ and docs/models/<name>/llm-eval-card.md

The pipeline folder holds prompts, schemas, code, the evaluation set and results; the evaluation card documents accuracy, failure modes, human review and monitoring. Every run saves its results to output/<run-id>/ in the model folder, with a run log (.claude/rules/model-code.md).

Gate / verdict

  • Confidentiality approved
  • Evaluation on a labelled set meets agreed thresholds
  • Human review defined
  • Every extracted number is traceable to its source
  • Evaluation is rerun after any model or prompt change

Suggested next steps

  • /ai-audit
  • /validate-model

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.