SKILLEMALL.ai

AF run-without-you

Phase 4 of building a Claude Managed Agent — make it run without you. Turn a graded agent into a recurring scheduled deployment (POSIX-cron), an event-driven curl trigger, or confirmed on-demand use, then finalize the versioned roadmap. Use when the user says "run it every morning", "put it on a schedule", "nightly", "weekly", "automate this", "make it recurring", or when the orchestrator routes phase=run-without-you. deployment_builder.py builds the POST /v1/deployments payload (initial_events must include user.message; optionally nests a user.define_outcome so each firing self-grades); cron_validator.py validates the 5-field cron + IANA timezone and prints the wall-clock DST note; next_directions_writer.py writes NEXT-DIRECTIONS.md. No tool makes API calls — the deployment is created via BYOK curl. Distinct from grade-iterate (the in-session loop) and wrap-up (closeout).

alirezarezvani/claude-skills Agent Skills author: alirezarezvani MIT 5 files body ≈ 791 tokens Open the sourcegithub.com analyzed 2 d ago

Phase 4 of building a Claude Managed Agent — make it run without you.

As a process F 39/100 · Will not run — References files that are not bundled: ../../references/loops-and-workflows.md

GeneratorInfrastructureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
F
39/100
Will not run
References files that are not bundled: ../../references/loops-and-workflows.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../references/loops-and-workflows.md
  • note frontmatter-key unknown frontmatter key "compatible_tools"

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: ../../references/loops-and-workflows.md
  • 0Tools and files. 1 referenced file(s) missing: ../../references/loops-and-workflows.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 12 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 16 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 791 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 885: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 6 example trigger phrases
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 16 items
  • +4Has examples (3 code blocks)
  • +3All 3 scripts are documented
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.