GTD Runner Skill
SkillMediaAutonomous task execution from GTD.md items. Use when processing GTD tasks, call prep, outreach, or podcast preparation.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the GTD Runner Skill skill
What this skill tells your AI
The instructions your AI receives, as published by gerstep/cybos in .claude/skills/GTD/SKILL.md and read by ahel’s review.
Autonomous task execution from GTD.md items.
Trigger
- Command:
/cyber-gtd - Default: plan-first (show before execute)
Workflow
- Read
@GTD.md→ extract items from# Next - For each item:
- Classify → match pattern to workflow
- Lookup entities via database:
bun scripts/db/query.ts find-entity "<name>" - Plan actions
- Show plan → ask to execute
- Execute approved items sequentially (one at a time)
- Output:
~/CybosVault/private/content/work/MMDD-<slug>.md
Classification → Routing
| Pattern | Confidence | Workflow |
|---|---|---|
| "ask for call", "message", "email", "reach out" | High | → workflows/outreach.md |
| "call with", "meeting", "X <> Y", "sync" | High | → workflows/call-prep.md |
| "podcast" | High | → workflows/podcast.md |
| company name, "research", "DD", "look into" | Medium | → workflows/research.md |
| no match | Low | Best judgment → log to learnings.md |
Entity Lookup
Query database for entity context:
- Parse item for names (people, companies)
- Run:
bun scripts/db/query.ts find-entity "<name>" --json - If found, get full context:
bun scripts/db/query.ts entity <slug> --json - Entity context includes:
- Recent interactions (calls, emails, telegram)
- Deal associations
- Pending items
- If not found + confident it's an entity:
- High confidence (company with domain) → auto-create stub
- Medium confidence → ask: "Create entity file for X?"
Output Format
All outputs to ~/CybosVault/private/content/work/MMDD-<slug>.md:
# Task: [Task Description]
**Status:** Pending Approval | Completed | Incomplete
**Created:** YYYY-MM-DD HH:MM
**GTD Item:** [Original text from GTD.md]
**Workflow:** [Which workflow handled this]
---
## Context
**Entity:** [Name]
- Type: [person/org]
- Deal: [link if exists]
- Previous calls: [N calls found]
**Key Info:**
[Relevant context from calls, deals, entity files]
---
## Draft
[Message/agenda/questions/etc]
---
## Pending Actions
- [ ] Send via Gmail to email@example.com
- [ ] Alternative: Telegram @handle
---
## Execution Log
- HH:MM - [action taken]
Staged Execution
Agent completes what it can autonomously:
- Research and context gathering
- Draft creation
- Preparation work
Then queues actions requiring approval:
- Sending messages (Gmail, Telegram)
- Scheduling meetings
- Any external action
Suggestions
When processing tasks, if you notice 3+ similar patterns that don't have a dedicated workflow, suggest: "I've seen '[pattern]' multiple times. Want me to create a workflow for it?"
Self-Improvement
Log all task executions to @learnings.md for pattern analysis.
Signals
- GitHub stars
- 105
- Forks
- 22
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
gtd- Source
- github.com/gerstep/cybos