keep-the-record
Records what the owner says about work their Andrew Rendon setup did for them. Use whenever the owner mentions what they did with drafts a job made (sent them, sent them untouched, changed or rewrote them, deleted or binned them), corrects how something should be done, or says something about the business has changed. Use it even when it is an aside or an FYI, or comes alongside another request.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
When the owner says what happened to a job's drafts, call the andrewrendon connector's record_verdict tool with the job and three counts: sent as written, changed first, not sent. Work the counts out from what they said. Ask only if the numbers cannot be worked out.
When the owner corrects how something should be done, or says a rule or a fact about the business has changed, call the andrewrendon connector's record_correction tool with their exact words. Then do what its reply asks: when the business keeps a company brain, the reply says which documents to update, and the update is part of recording it.
Then say in one line what was recorded, and carry on with anything else they asked for.
- Repository
4W-dev/andrewrendon-plugin
- Revision
ea0681a
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.