메뉴
Use this skill when the user wants a memory feed — a scheduled automation that fetches targeted data from their integrations (gmail/calendar/slack/web) and keeps ONE memory page current, updated in place. Examples; "track my PR queue", "keep an invoices page", "week-ahead brief".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Implement a spec end-to-end — recon readers map the codebase, an architect pins every cross-file contract in a blueprint, parallel builders implement disjoint workstreams from it, adversarial review, then a final test gate. Use for multi-file feature work. Run via the workflow tool by name.
Find -> adversarially verify -> rank issues over a target (a diff, dir, file, or glob). Use for code review, a scoped bug hunt, a security or perf pass. Run via the workflow tool by name.
Answer a question about a target by fanning out parallel readers over derived angles, then synthesizing a cited answer. Use to understand a subsystem, research a question, or trace how/where something works. Run via the workflow tool by name.
Decide between approaches — generate N diverse proposals from different lenses, score each against criteria with independent judges, then synthesize a decisive recommendation. Use for design choices, tradeoff calls, "which approach should we take". Run via the workflow tool by name.
Use this skill when the user wants to turn the current conversation into a scheduled automation. Analyze the session and call create_automation to propose one — the user reviews the full prompt + schedule in the approval card before it's saved.
Create a custom user tool in ~/.ntrp/tools/ using the current tool(...) API.
| name | add-feed |
| description | Use this skill when the user wants a memory feed — a scheduled automation that fetches targeted data from their integrations (gmail/calendar/slack/web) and keeps ONE memory page current, updated in place. Examples; "track my PR queue", "keep an invoices page", "week-ahead brief". |
A feed is a scheduled automation that owns one memory page under feeds/ and rewrites it in place every run. The page is the current state of one question ("what's in my PR queue?"), not a log. This replaces raw per-integration ingest with targeted, user-shaped briefings.
Your job: clarify the target if needed, then call create_automation once. The user reviews the prompt + schedule in the approval card.
feeds/<slug>.md, slug from the question ("pr-queue", "invoices", "week-ahead").memory_write. Never append, never keep history — the automation run log is the history.Call create_automation once:
name: short, the question — e.g. "PR queue feed".trigger_type / schedule: match the data's cadence — a PR queue is every: "2h" on weekdays; a week-ahead brief is at: "07:30", days: "daily". Don't over-poll slow data.auto_approve: true — a feed must run unattended (memory_write is approval-gated otherwise).description (the prompt the feed runs on): use this template, filled in:You maintain the memory page `feeds/<slug>.md` — a briefing that answers: <the question>.
1. Read the current page first, then fetch only what's needed to answer the
question, using <specific integration tools / sources>.
2. If nothing MEANINGFUL changed versus the current page, STOP — no rewrite, no
timestamp bump. Your run is logged either way; the page's stamp means "last
meaningful change", and the automation's run history means "last checked".
Be ruthless about this: a feed that rewrites cosmetic diffs is noise and cost.
3. Otherwise rewrite the page with `memory_write` (full page, update-in-place):
- `# <Title>` then a one-line answer/summary.
- Compact sections or a table for the items (tabular data belongs in a table).
- Lead with what needs action; drop resolved items entirely.
- End with `_Changed <date/time>._`
- Keep it under ~40 lines. Stale content is worse than missing content.
4. If a run surfaces a DURABLE fact (a decision, a person, a standing change),
call `remember` for it — the page is transient state, records are memory.
When the user's ask matches one of these, start from it (adjust sources/cadence to their setup) instead of inventing a shape. Focused feeds beat a generic "email feed".
| Preset | Question the page answers | Cadence |
|---|---|---|
pr-queue | Which PRs wait on me (review, CI red, unresolved threads)? | every 2h, weekdays |
work-blockers | What is blocked and on whom — mine and what I block for others? | every 4h, weekdays |
job-applications | Where does each active application/interview process stand? | daily 09:00 |
billing-security | Unusual charges, quota/limit warnings, security alerts needing action? | daily 08:00 |
week-ahead | Commitments, deadlines, and travel in the next 7 days? | daily 07:30 |
invoices | Which invoices/acts are unsent, unsigned, or unpaid? | weekly mon 10:00 |
memory_write will refuse; feeds live under feeds/.create_automation call. Before it, 2-3 sentences: what feed, why this schedule.