Source profileQuality 77/100

griffinwork40/agent-afk/src/bundled-plugins/awa-bundled/skills/automate/SKILL.md

automate

Set up a scheduled headless afk run that pushes a summary to Telegram. Use when the user wants to automate a recurring task via the afk daemon scheduler (cron) with push-notified results.

Source repository stars
45
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Set up a scheduled headless afk run that pushes a summary to Telegram.

Best for

  • Use when the user wants to automate a recurring task via the afk daemon scheduler (cron) with push-notified results.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/griffinwork40/agent-afk --skill "src/bundled-plugins/awa-bundled/skills/automate"
Safe inspection promptEditorial

Inspect the Agent Skill "automate" from https://github.com/griffinwork40/agent-afk/blob/803066d4f1e0cd57e983658dc670d647fcd893c9/src/bundled-plugins/awa-bundled/skills/automate/SKILL.md at commit 803066d4f1e0cd57e983658dc670d647fcd893c9. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

The source does not provide enough structured workflow evidence for a step-by-step guide.

Permission review

Static risk signals and limitations

Reads files

low · line 4

The documentation asks the agent to read local files, directories, or repositories.

**Scout** — call `list_schedules` and inspect `~/.afk/config/schedules.json` for existing or overlapping jobs, run `afk service status` to see whether the daemon is installed as a launchd service and running, confirm Telegram is configured

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score77/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars45SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
griffinwork40/agent-afk
Skill path
src/bundled-plugins/awa-bundled/skills/automate/SKILL.md
Commit
803066d4f1e0cd57e983658dc670d647fcd893c9
License
Apache-2.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

Set up a recurring headless task using afk's native scheduler. Do NOT hand-roll launchd plists or shell scripts — afk has first-class scheduling: the create_schedule tool writes ~/.afk/config/schedules.json entries that afk daemon runs on cron.

Dispatch two sub-agents in parallel:

  1. Scout — call list_schedules and inspect ~/.afk/config/schedules.json for existing or overlapping jobs, run afk service status to see whether the daemon is installed as a launchd service and running, confirm Telegram is configured (TELEGRAM_BOT_TOKEN + AFK_TELEGRAM_ALLOWED_CHAT_IDS), and scan the target project folder for conventions. Report conflicts, daemon/service state, and any missing prerequisite.
  2. Prompt designer — draft the recurring task's command string: a self-contained prompt (or /skill --flags invocation) sent verbatim into a freshly spawned session each run. The daemon session starts cold, so encode all input context explicitly, and require the run to END by calling the send_telegram tool with a concise, push-ready summary.

When both return:

  • If Telegram is unconfigured, stop and tell the user to run /telegram-setup first — send_telegram fails closed without TELEGRAM_BOT_TOKEN and AFK_TELEGRAM_ALLOWED_CHAT_IDS.
  • Create the job with the create_schedule tool: name, the designed command, the requested 5-field cron, trigger: "cron", and notifyOn: "failure" as a crash safety-net (the per-run summary comes from the agent's own send_telegram call, not from notifyOn).
  • Schedules only fire while the daemon is running, so make it survive reboot/crash: if afk service status shows the daemon isn't installed, run afk service install daemon (launchd RunAtLoad + KeepAlive on macOS).

Dispatch a verification sub-agent to confirm the job registered (list_schedules), the daemon is running (afk service status), and — by running the task's command once as a one-shot (afk chat "<command>") — that the Telegram summary actually arrives. On failure, diagnose (Telegram config, daemon not running, cron syntax, prompt shape) and fix before exiting. Report the schedule id, cron, notifyOn, daemon/service status, and the next scheduled run.