agentleFS
IamK77IamK77/Skill/skills/inquiry/forge/SKILL.md

forge

Skill2 starsChanged 31 days agoApache-2.0View on GitHub

Execute a defined research experiment with traceable inputs, configurations, runs, and outputs. Use for experiment implementation and reproducibility, not to invent the research claim.

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use forge-ship, forge-review and 10 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.
  • redteamlifeSkill

    forge-ship

    Use when the user asks to merge, release, promote, reconcile, or close out work in a repo containing `docs/forge/` or governed by FORGE. Not for per-task commits; those complete inside forge-execute-task.

    Also in 6 projects that use this

  • tonmoy007Skill

    forge-review

    Run a multi-dimensional parallel code review over the current change.

    Also in 8 projects that use this

  • weselbenSkill

    forge-docs

    Load before code changes, before writing docs or an ADR, when a user question exposes a missing how-to, and when closing a chunk of work; also loaded by forge after each squash-merge and by deep-research after a report.

    Also in 3 projects that use this

  • DailenGSkill

    forge-design

    Design, UX, and polish discipline for the forge lifecycle. Covers the design tier, the design brief in docs/DESIGN.md, UX requirements and their verification methods, the per-slice design pass, the UX defect register, and the release polish pass. Load whenever work touches a user-facing surface (GUI, terminal, library API, or operated service), whenever a UX observation needs disposing of, and whenever a release is in reach.

    Also in 3 projects that use this

  • DshamirSkill

    forge-plan

    Takes analysis.json + budget cap → derives the full phase sequence, hyperparameters, instance type, cost estimate, and acceptance thresholds. Emits plan.md (the single human gate document) and plan.json (the machine-readable spec that dispatch-v2 consumes). Refuses to plan if estimated cost exceeds budget×1.2.

    Also in 4 projects that use this

  • tonmoy007Skill

    forge-build

    Run Stage 6 of the Forge pipeline — implementation. Use when the user says

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    When this stage is fulfilled: checklist advance prepare --run "$RUN".

    line 41
  2. Distinctive:

    Run within the agreed budget.

    line 45
  3. Very specific:

    Run manifest and analysis inputs are available for independent review.

    line 64
  4. Distinctive:

    If resources or data are unavailable, report the blocked run rather than substitute synthetic results silently.

    line 71
  5. Very specific:

    If an input or permission is missing, name the blocker and leave the relevant item pending.

    line 73
  6. Very specific:

    After all required work and stage closures is recorded, use checklist done --run "$RUN".

    line 79

“Common” is measured: kept by at least 6 in 10 of the 67 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
<!-- Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0. See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0 -->

forge

Execute a defined research experiment with traceable inputs, configurations, runs, and outputs. Use for experiment implementation and reproducibility, not to invent the research claim.

Inputs

Versioned experimental plan; implementation; data access; environment; compute authorisation and budget.

Run record

Use checklist 0.5 or newer for this SOP. Reading or reloading the skill must not reset work. For a new task, run checklist init "${CLAUDE_SKILL_DIR}" --new --path "/absolute/project"; retain its returned ID as RUN. For existing work, use checklist resume "$RUN", then checklist show --run "$RUN". Outside Claude, replace the skill-directory variable with this directory’s actual path.

Commands below record work after it is done. Replace evidence placeholders with concise artifact locations and observations. Manual confirmations are not independent proof; a sensor pass covers only the command and inputs it observed. verify does not close a stage; advance checks that its required readings are fulfilled. Use report --run "$RUN" for the retained history.

Procedure

prepare

Match code, data, and configuration to the plan. Run a small end-to-end sanity check and verify that metrics and failure records have the intended meaning.

Record these artifacts after doing the work:

  • Code, data, environment, and plan versions are recorded. checklist check prepare inputs --run "$RUN" --evidence "<artifact and observation>"
  • A small end-to-end run validates data flow and metric computation. checklist check prepare sanity --run "$RUN" --evidence "<artifact and observation>"

When this stage is fulfilled: checklist advance prepare --run "$RUN".

execute

Run within the agreed budget. Preserve seeds, commands, logs, failed runs, and deviations; checkpoint where useful. Keep exploratory adjustments separate from the committed comparison.

Record these artifacts after doing the work:

  • Successful and failed runs have reproducible configurations and logs. checklist check execute runs --run "$RUN" --evidence "<artifact and observation>"
  • Plan deviations and data-boundary checks are recorded. checklist check execute integrity --run "$RUN" --evidence "<artifact and observation>"

When this stage is fulfilled: checklist advance execute --run "$RUN".

package

Regenerate at least a representative result from saved inputs and document the remaining reproduction cost. Package raw-to-summary transformations, not only final charts.

Record these artifacts after doing the work:

  • A representative result was regenerated from recorded inputs. checklist check package reproduction --run "$RUN" --evidence "<artifact and observation>"
  • Run manifest and analysis inputs are available for independent review. checklist check package artifacts --run "$RUN" --evidence "<artifact and observation>"

When this stage is fulfilled: checklist advance package --run "$RUN".

Branches

If resources or data are unavailable, report the blocked run rather than substitute synthetic results silently. A method change that changes the comparison returns to ledger for a new plan version.

If an input or permission is missing, name the blocker and leave the relevant item pending. A changed requirement may need a new run; an accepted checklist edit uses resume "$RUN" --refresh and requires fresh readings. To abandon work, use checklist reset --run "$RUN" --reason "<reason>"; history is retained.

Completion

A traceable experiment artifact set for reckoning and envoy; resource use stays within explicit authorisation.

After all required work and stage closures is recorded, use checklist done --run "$RUN". This archives the result without deleting its history; it does not authorise any external action.

Reference shelf

Open the technique relevant to the current step. These notes provide concrete methods and examples, not additional phases; this entrypoint defines the run's completion conditions.

  • Preserve the identity and failures of a research run
  • Validate the path from input data to reported metric
  • Regenerate a result from retained artifacts
  • Execute a plan without hiding methodological changes

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.