원클릭으로
delegation-tracker
// Track delegated commitments, set follow-up timers, and generate nudge reminders when updates are overdue.
// Track delegated commitments, set follow-up timers, and generate nudge reminders when updates are overdue.
Linear issue tracker API integration. Covers first-use identity bootstrap (viewer + teams cached), raw GraphQL for list/search/create/update, and the rules for handling "my issues" / "assigned to me" requests.
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a `commitments` project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
Compose and deliver summaries of open commitments, deadlines, pending signals, and resolution suggestions.
One-time setup for the commitments tracking system. Creates workspace structure, schema docs, and installs triage and digest missions. Excluded from activation once `projects/commitments/README.md` exists in the workspace (the file this skill writes as its first step).
Recognize obligations in conversation, extract signals with immediacy and expiration, create and manage commitments in the workspace.
One-time onboarding for the content creator workflow — content pipeline stages, trend expiration, cross-platform cascades, heavy idea parking. After successful setup this skill is excluded from selection until the marker file is deleted.
| name | delegation-tracker |
| version | 0.1.0 |
| description | Track delegated commitments, set follow-up timers, and generate nudge reminders when updates are overdue. |
| activation | {"keywords":["delegated","assigned to","waiting on","follow up with","check with","ask them","handed off","they said","blocked on","no response","nudge","chase up"],"patterns":["(?i)(delegated|assigned|handed off) (to|this to)","(?i)(waiting|blocked) on .+ (to|for)","(?i)follow up with .+ (about|on|regarding)","(?i)check (with|in with) .+ (about|on)","(?i)(tell|ask) .+ to .+"],"tags":["commitments","delegation"],"max_context_tokens":1200} |
Track commitments that depend on someone else. The triage routine will flag stale delegations for follow-up.
User says: "I asked Sarah to handle the deployment" or "tell ops to investigate staging" or "waiting on legal for the contract review."
This skill is only successful if the delegation is persisted in workspace memory. Do not just acknowledge or summarize a delegation.
Execution order is mandatory:
projects/commitments/open/Never say "tracked", "saved", or "I'll flag it" unless the corresponding
memory_write succeeded.
Action:
projects/commitments/open/ via memory_searchdelegated_to: <person/team>, status: waitingprojects/commitments/open/ with:---
type: commitment
status: waiting
urgency: <infer from context>
due: <if mentioned, else null>
created_at: <today>
owner: user
delegated_to: <person or team name>
source_signal: null
tags: [delegation]
---
# <What was delegated>
<Description of what was delegated and to whom.>
## Follow-up
- Delegated on: <today>
- Expected response by: <date if given, else 3 days from now>
- Last checked: never
User says: "Sarah got back to me about the deployment" or "legal approved the contract."
Action:
memory_search or memory_tree("projects/commitments/open/")projects/commitments/resolved/open or waitingThe triage routine handles automated follow-up detection. It reads open commitments where delegated_to is set and status: waiting, checks the "Expected response by" date, and flags overdue items in the triage alert.
When the user asks to follow up explicitly ("nudge Sarah about the deployment"), draft a brief follow-up message and offer to send it if a channel to that person is available.