Package a repeated task with a clear contract.
The problem
Explaining a familiar procedure from scratch makes it easy to omit a step. A bare tool name also says little about when or how it should be used.
An explanatory exhibit
A reusable skill describes more than a tool
Two conceptual skill contracts explain the pattern; these are not complete executable instructions.
- 01
Trigger
A named workflow fits the task
- 02
Procedure
Inputs · tools · evidence · limits
- 03
Output
A predictable result to review
Inspect the consequence
Archive recall
One detail with a source
FindThat selects the relevant corpus and retrieves the supporting record.
Browser walkthrough
A captioned document
Flow screenshots PDF needs ordered captures and a reviewed, readable artifact.
What this makes possible
I keep repeatable workflows as named skills with their inputs, tools, output shape and limits close together.
Source information sheet
Evidence, implementation & history Implementation inspected
What I checked
Skill directories and shared-link documentation inspected. No claim about the number of installed skills is made.
Research cut: 14 October 2026. Source areas below are from metaclaude and metacodex. Private conversation references are retained in the research ledger and are not published here.
Implementation decisions
A skill supplies a procedure when a task calls for it: where to read, which tools to use, what to return and how to handle known failure boundaries.
Both workbenches contain portable skills. metacodex’s shared directory link makes the maintained skill set available without copying each file into runtime state.
A path through the feature
- Choose the relevant workflow
Invoke the named skill when its scope matches the requested task.
- Read the contract
Follow its inputs, evidence and output requirements. Apply the user’s scope and preferences to the work.
Source areas
metaclaude/skills/metacodex/skills/metacodex/README.md
The small explanatory exhibit uses invented records to describe the mechanism. Separate recordings and working examples carry their own evidence notes.
Recorded history
Dates describe the researched record, rather than today’s deployment.
Building a versioned coding-assistant configuration
FindThat archive recall skill