القائمة
Read knowledge-map.json snapshots correctly. Distinguish facts (what exists today) from signals (evidence of recent change).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Load when reading or writing project notes, weekly/monthly summaries, or journal/agent.md. Owns GET/PATCH for context files except today.md and roadmap.md, which use their dedicated skills.
Load when the user wants an ongoing task on a fixed cadence (every morning, each Monday, hourly) to run autonomously as its own named recurring Agent. Creates it via POST /api/agents. Not for one-time reminders (use schedule) or app-data background fetches (use managed-tasks).
Load to manage the durable source library (user-sent PDFs/PPTX/docs) — list unfiled sources, file them as knowledge/sources/ cards, promote images, or send a stored source back. SKIP for delivering files you generated this turn (attach) or general vault edits (context).
Hand a long-running or open-ended task (deep research, multi-repo CI audit, monitor X over time, bulk compile) to /api/background-task. Compose a self-contained brief, set the notification policy, POST, ack, end the turn. Read GET /:id for follow-up detail.
Read-only Task Board — list everything in motion (recurring DMs, Agents, app-fetch, automation triggers, reminders, background/browser work) via GET /api/tasks, and preview a delete's blast radius via GET /api/tasks/impact. For writes use the `task` skill.
Hand open-ended browser requests (post a tweet, fill a contact form, check an order status, …) to /api/browser-task. Relay sub-agent clarifications, POST /clarify with the reply, /cancel on stop.
| name | knowledge-map |
| description | Read knowledge-map.json snapshots correctly. Distinguish facts (what exists today) from signals (evidence of recent change). |
| allowed-tools | ["Read"] |
The file data/knowledge-map.json in your workdir is a structural
snapshot of ~/.personal-agent/context/ taken at run start. It is the
ground truth for "what files exist and what headings they contain right
now." Use it for paths_resolve / sections_resolve validation BEFORE
submitting a proposal.
{
"context_dir": "/Users/.../personal-agent/context",
"taken_at": 1717000000000,
"files": [
{
"path": "identity/profile.md",
"headings": ["Identity", "Work Pattern", "Learned Context"],
"frontmatter": { "type": "profile", "owner": "shared" },
"last_modified_at": 1716900000000
},
...
]
}
scope_paths (e.g. user/*.md) are NOT pre-expanded —
match yourself.headings[] order is document order, leading ## / ### already
stripped.frontmatter is a flat string→scalar object (no nested YAML).A knowledge_layout payload's files[] SHOULD agree with the snapshot's
files. When they diverge:
additive opportunity.destructive
proposal, but ONLY propose if signals corroborate (a file_remove
structure_diff, an owner_correction, etc.).additive (heading
added since last overlay).destructive,
same corroboration rule.cross_references payloads from snapshot adjacency alone.
"Two files in the same directory" is not evidence of a relationship.
Cross-references require an explicit citing signal.frontmatter_schema reduction (drop a required[]
entry) — schema reduction is a separate human PR. The smoke test
rejects this anyway.last_modified_at < 7 days ago → "fresh", may be in flux.last_modified_at older than 60 days, unchanged → "stable", safe to
treat as permanent layout.