Skills, Then Connectors, Then Automation
Pack an accepted method as a skill, connect external services for this job, and only then let it run on a rule. Reverse the order, and permission opens before the method exists.
What WorkBuddy adds is not “more features.” It can fold one success into a method you can rerun, and connect that method to external services. The blue book puts skill design, connectors, and automation reliability after onboarding and cases. The order is the judgment: a container must not arrive before the method.workbuddy-guide
After reading, you should be able to answer:
- When should a skill, a connector, and automation appear?
- Why is automation not a permission upgrade?
- Why are human stops still there?
Three containers
- Skill: pack the five things you already accepted; next time, swap the object. Do not skill a job that has never been accepted.
- Connector: the external service this job needs to see or write, smallest connection, revoke after. Not “connect everything it can.”
- Automation: the same skeleton runs itself while the rule is stable. Failures stop. Irreversible acts still need a person. Automation copies the method. It does not delete red lines.
Automation still has to stop
Reliability is not “it will run because you set it.” It is visible failure, a stop, and a rollback. Same stops as watch, stop, take over, triggered on every run instead of this run. Permission grading is in red lines.