Start with a small task: turn meeting notes into an action list. The input is the meeting record; the output contains actions, owners, deadlines, and supporting text. Mark missing information as unconfirmed.
Use stable, descriptive folder and skill names.
Put required output templates in assets/ and reference their paths in the instructions. Place longer rules in references/ and load them only when relevant. Add scripts only when needed.
Open Extensions → Skills → Add skill and follow the client's available import method. Run a task that matches the description. Check that the skill is used, resources are readable, output fields are complete, and every action has evidence. Test locally before submitting to the marketplace.
Next: check the specification, prepare a self-test report, then publish the skill.
Create and add a skill
On this page