Skills
A versioned procedure for a type of job: the sequence, tools, checks, output format, and stop conditions.
A weekly metrics pack, a release process, a service investigation, or a publishing workflow can each become a Skill. The Skill is the method; the operating package is that method plus the connections, Knowledge, permissions, and checks it needs to run safely.
Creating one from a successful run
A successful run is the best source for a Skill. Several good examples help Opulent separate the stable procedure from one-off details, which is why it is worth waiting for the second or third clean run rather than packaging the first.
Improving one that performs poorly
Compare successful and failed sessions. Update the smallest part that explains the failure: an input check, a tool sequence, an exception rule, an output schema, or a validation step. Test the candidate on a held-out case before broad use.
Resist rewriting a Skill wholesale after one bad run. A wholesale rewrite changes the parts that were working along with the part that was not, and you lose the ability to tell which change helped.
What belongs in a Skill
- The sequence of steps, in order.
- The tools each step may use.
- The checks that must pass before the next step.
- The output format, so downstream work can rely on it.
- The stop conditions, including what routes to a person.