菜单
Captures a product, agent, or monument idea into the repo ideas backlog from the current chat. Use when the user asks to capture an idea, park an idea, idea backlog, brain dump, feature wishlist, "note this for later", or similar—without turning it into a full decision log entry.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate multi-lens narratives for Bride of Charlie from structured data (episodes, claims, graph, social threads); support claim-constraint relaxation for alternate tellings; align book-app chat with meta-layer sources. Use when authoring BOC stories, book-app copy, or enabling others to narrate from the same evidence base.
Plans and operates Discord for Pacha (family-safe, slate/community) and Meta-Layer (governance, DPs, gov hub handoffs): channel maps, mod norms, escalation, announcements, and what belongs in Discord vs GitHub. Use when the user mentions Discord, server setup, moderation, Pacha Discord, meta-layer Discord, community rules, or bot/workflow hooks for servers.
Drafts Desirable Property text and inscription-ready variants from app.themetalayer.org DP sources, applying the full meta-layer lens. Saves outputs to the agent-lab Draft Editor via save_draft when available. Produces article-first or video-first companion assets and CTAs for comments and supporting/opposing artifacts. Use when working on DP drafts, on-chain inscription text, gov hub copy, meta-layer properties, Draft Editor, or "draft DPn / desirable property / inscription."
Ingest documents from Google Drive into the meta-layer knowledge graph. Converts Word docs, PDFs, and Google Docs to structured knowledge, extracts concepts, and adds to Neo4j. Use when the user wants to process Drive documents, mentions "ingest from Drive", "add Drive docs to graph", or needs to organize Google Drive content into their knowledge base.
Organize Google Drive documents using meta-layer concepts and knowledge graph relationships. Auto-categorizes documents, creates folder structures, generates knowledge maps, and maintains semantic organization. Use when user wants to "organize Drive by concepts", "restructure Drive folders", "categorize documents", or "create knowledge-based Drive organization".
Monitor Google Drive folders for new or updated documents and automatically trigger ingestion workflows. Sets up webhooks and polling to detect changes. Use when user wants to "watch Drive for changes", "auto-ingest new documents", "monitor Drive folder", or set up automated document processing.
| name | capture-idea |
| description | Captures a product, agent, or monument idea into the repo ideas backlog from the current chat. Use when the user asks to capture an idea, park an idea, idea backlog, brain dump, feature wishlist, "note this for later", or similar—without turning it into a full decision log entry. |
Draft a short, durable idea record the user can paste into—or the agent can append to—the ideas ledger.
docs/IDEAS_BACKLOG.md (agent-lab root). If missing, create it from the template in that file’s top comment or the structure below.
One entry (newest at top of the ## Ideas list unless user asks to append at bottom):
### YYYY-MM-DD — <5–8 word title>
- **Idea:** One tight paragraph: what and why it might matter.
- **Tags:** e.g. `agent`, `monument`, `neo4j`, `comms`, `skill` (optional)
- **Inspired by:** This Cursor chat / meeting / reading (optional)
- **Next step:** One concrete next action, or "TBD"
No secrets. No client PII unless user explicitly wants it.
docs/IDEAS_BACKLOG.md, insert the new ### block immediately after ## Ideas (before older ### entries), save.If the idea is only about Bride of Charlie monument narrative or rollout, offer a path under projects/monuments/bride_of_charlie/docs/IDEAS_BACKLOG.md instead or in addition—only if the user wants monument-local ideas separated.