Skill
Document a reusable skill.
A skill is a reusable piece of work. ISATVON asks you to document its trigger, action, acceptance check and handoff, so another reviewer can understand what it does and where it stops.
The skill uses the same seven sections as any ISATVON specification: Instructions, Source, Automation, Tech Stack, Variables, Outcome and Notification.
Trigger and Source
State when the skill runs and which source material it may use.
Action and Tech Stack
Describe the action and the systems used. A tool name is not evidence that an integration is implemented or tested.
Document a Reusable Skill
Record the trigger, action, acceptance check and handoff:
Trigger and Source
Action and Tech Stack
Acceptance Check
Handoff and Review
Reuse Does Not Expand Permission
A reusable specification should carry the source and action limits with it.
1. Record the limits
Keep the source and action limits with the skill. Reuse does not expand permission.
2. Record the evidence
Note the version, test cases and acceptance checks, so another reviewer can understand what passed.
3. Mark what is unverified
Say what remains unverified, so the next reviewer does not assume it.
Why DigiBull AI for Skills
See the full ISATVON framework for all seven sections.
Frequently Asked Questions
What is a skill in ISATVON?
Which sections does ISATVON use?
Does reuse expand permission?
Does writing a skill down make it work?
How do we get started?
Want To Talk Through Skill Specification?
Start with one checkable skill.
Talk to DigiBull AI about the task you want to specify. Keep confidential material out of an initial enquiry.