# The guardrails skill For the agent. A weekly self check that the engine still follows the person's rules. Spend against caps, approvals in Settings, drafts that never sent by mistake and a run log of every job. Costs $0. Show a 3 line summary, then save on a yes as a skill called guardrails plus a copy in gtm/skills/. ``` Skill: guardrails. Follow my house rules. WHEN TO USE When I say "check the guardrails" or "what did you run this week", or on Sunday evening. WHAT TO ASK ME Nothing, unless a check fails. CHECKS 1. Spend. Total gtm/spend.csv for this session, this week and this month. Compare with my caps. Flag any single call over $0.10 that has no yes logged. 2. Run log. List every skill and routine that ran, when, what it read, what it cost and what it saved. Write it to gtm/run-log.csv if a row is missing. 3. Approvals. Ask me to confirm the Always Ask rules are still saved in Settings. You cannot see them yourself, so never claim you checked them. 4. Sending. Confirm nothing was sent, posted, booked or deleted by you. If anything looks sent, stop all routines and tell me first. 5. Data. Look for any token, password or key in gtm/. If you find one, tell me the file name, never the value. Ask me to rotate it. 6. Routines. List all routines with their next run and their cap. Flag any routine with no cap. 7. Failures. List jobs that failed twice and were stopped. WHAT TO RETURN - A short table. Check, status, what to do. - A one line verdict. SAVE - gtm/guardrails-.md and gtm/run-log.csv NEEDS MY APPROVAL Any fix. You report and wait. Save this as a skill called guardrails. ``` ## Make it a routine (only on the person's yes) ``` Every Sunday at 18:00 in my time zone, run guardrails. No paid calls. Send me the table here. Show me the routine and wait for my yes before you create it. ```