メニュー
File new articles, transcripts, and notes into knowledge/ in the right place with source metadata and an evidence tag.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/CleanExpo/Unite-Group --skill ingestコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| name | ingest |
| description | File new articles, transcripts, and notes into knowledge/ in the right place with source metadata and an evidence tag. |
Input: a new resource — article, transcript, note, Obsidian export, or a URL.
Classify the resource:
knowledge/board/<advisor>/ (create the
advisor folder + profile.md stub if new).knowledge/notes/.knowledge/frameworks/.File it as Markdown with a metadata header:
---
source: <URL, "user", or original filename>
ingested: <YYYY-MM-DD>
evidence: <verified | unconfirmed> # verified only if the source is checkable
topic: <few words>
---
Don't silently rewrite. Preserve the original content; add structure (headings, speaker labels for transcripts) only where it aids retrieval.
Report back: where it was filed, under what evidence tag, and which
skills will now pick it up (e.g. a new advisor becomes visible to
ask-the-board).
When given a zipped Obsidian vault or a batch of transcripts: propose a filing plan first (counts per destination folder), get approval, then ingest. Flag anything that looks like a secret or personal credential instead of filing it.
The authoritative environment-variable registry for the Unite-Group Nexus. Use whenever adding, reading, renaming, or debugging an env var or secret — new integration config, a `process.env.X` read, an auth/OAuth wiring, a cron secret, a "which variable holds this" question, or a "works locally but not in prod" symptom. Also use before pinning any variable name in code, and when reconciling the two credential planes (Vercel prod vs the local hermes fleet). Prevents the `APIFY_API_KEY` vs `APIFY_API_TOKEN` class of drift.
Create, verify, and promote Supabase schema changes via database branches. Every schema change/migration must be validated on a Supabase database branch before prod (see CLAUDE.md line 44).
Verify production Supabase schema before shipping code that touches it. Use BEFORE writing or reviewing ANY code that reads or writes a Supabase table in the Nexus — new queries, inserts, updates, CHECK-constrained values, RLS-dependent reads, cron data access — even one-line changes and even when the table "obviously" exists. Also use immediately when a query fails with "column does not exist", when inserts appear to succeed but produce no rows, or when generated TypeScript types disagree with runtime behaviour.