ワンクリックでManusで任意のスキルを実行

personal-knowledge-routing

スター14

フォーク1

更新日2026年6月17日 11:36

Route durable personal context and reusable knowledge between augmentedcode-configuration and the personal knowledge vault. Use when the user asks to remember, persist, capture, retrieve, or organize personal knowledge; when deciding whether information belongs in rules, skills, portfolio, notes, maps, or inbox; or when using personal-knowledge-vault as a low-context reference layer.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

saski

saski/augmentedcode-configuration

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Personal Knowledge Routing

Use this skill to keep agent instructions small while preserving durable knowledge in the personal knowledge vault.

Repositories

Agent configuration: /Users/saski/Code/augmentedcode-configuration
Personal vault: /Users/saski/Code/personal-knowledge-vault
Vault content root: /Users/saski/Code/personal-knowledge-vault/vault

First Files To Read

When working with the vault, start with:

vault/AGENT_GUIDE.md
vault/README.md
vault/_meta/conventions.md
vault/_meta/promotion-policy.md when moving content into more durable areas
vault/_meta/source-manifest.md when source material creates or changes durable content
The smallest relevant vault/maps/*.md, vault/portfolio/*.md, or vault/notes/*.md file

Do not read the whole vault unless the user explicitly asks for a full audit.

Routing Table

Information type	Destination
Agent behavior that must apply across tools	`augmentedcode-configuration/.agents/rules/`
Repeatable agent workflow or protocol	`augmentedcode-configuration/.agents/skills/`
Tool setup, symlink policy, validation scripts	`augmentedcode-configuration/`
Stable personal facts, preferences, goals, responsibilities, working agreements	`personal-knowledge-vault/vault/portfolio/`
Durable decisions and decision-making patterns	`personal-knowledge-vault/vault/portfolio/decision-log.md` or `vault/notes/`
Distilled reusable knowledge, source summaries, lessons, patterns	`personal-knowledge-vault/vault/notes/`
Navigation and topic indexes	`personal-knowledge-vault/vault/maps/`
Raw imports, unprocessed conversations, temporary captures	`personal-knowledge-vault/vault/inbox/`
Source provenance and promotion decisions	`personal-knowledge-vault/vault/_meta/source-manifest.md` and `vault/_meta/promotion-policy.md`
Vault schema, conventions, and maintenance policy	`personal-knowledge-vault/vault/_meta/`

Persistence Rules

Prefer references over copying: if the vault already contains the knowledge, link or cite the file path instead of pasting it into rules.
Update portfolio/ only when information is stable, reusable, and source-backed.
Apply the vault promotion policy before moving content from inbox/ to notes/ or from notes/ to portfolio/.
Update the source manifest when a source creates or changes durable notes, portfolio context, maps, or governance files.
Put uncertain or still-evolving material in notes/ or inbox/ first.
Keep raw conversations out of portfolio/.
Preserve user-authored vault content unless the user explicitly asks for a rewrite.

Context Discipline

Use maps and frontmatter as indexes before reading full files.
Read exact target files; avoid broad recursive reads.
If a task needs personal context, load the relevant portfolio file rather than embedding that context in AGENTS.md.
If a rule starts accumulating domain knowledge, move the knowledge to the vault and leave a short routing rule here.

Link Discipline

Before writing an Obsidian wikilink, verify that the target note exists.
If the target is uncertain, write plain text or a relative Markdown path instead of creating a broken wikilink.
After vault edits, run make check from /Users/saski/Code/personal-knowledge-vault.
The vault pre-commit hook and scheduled GitHub workflow also run make check.

Good Defaults

For "remember this about me": propose a concise portfolio/ update, then apply it only if the source is stable.
For "save this idea": create or update a notes/ page and link it from a relevant maps/ page.
For "capture this conversation": put raw or summary material under inbox/ or notes/, then propose any portfolio promotion separately.
For "make agents aware": add the smallest possible rule or skill pointer in augmentedcode-configuration, with details stored in the vault.

このリポジトリの他の Skills

同じリポジトリ

github-host-alias

saski/augmentedcode-configuration

Use when running git clone, git remote add, git remote set-url, or suggesting GitHub SSH commands to ensure all GitHub access uses the saski SSH host alias.

2026-06-1714

building-data-apps

saski/augmentedcode-configuration

Build modern data apps, dashboards, and interactive reports using either React + Vite or Streamlit. Includes optional Gemini Data Analytics chat integration for an AI powered "chat with your data" experience. Relevant when any of the following conditions are true: 1. User explicitly requests to build a data dashboard, data application, or visualization UI, and the UI pulls data from a GCP database (defaulting to BigQuery unless otherwise specified). 2. You need to generate a frontend web application to interact with, query, and visualize data from GCP data sources. 3. User wants to build a "chat with your data" experience or integrate the Gemini Data Analytics chat API into a web interface. Do NOT use when any of the following conditions are true: 1. The request is for building backend-only services. 2. The request is for simple CLI scripts or command-line applications. 3. The web application is not data-centric or does not involve visualizing/querying data from GCP sources.

2026-06-0314

gcp-spark

saski/augmentedcode-configuration

Develops and executes Spark code on Dataproc Clusters and Serverless. Reads and writes data using BigLake Iceberg catalogs, BigQuery and Spanner. Debugs execution failures. Use when: - Writing Spark ETL pipelines on GCP. - Training or running inference with ML models with spark on GCP. - Managing Spark clusters, jobs, batches, and interactive sessions. Don't use when: - Writing generic Python scripts that don't use Spark. - Performing simple SQL queries that can be done directly in BigQuery.

2026-06-0314

lustra

saski/augmentedcode-configuration

Use when the user wants to clean up AI slop, harden a codebase, or run technical due diligence: review code for security flaws and vulnerable or wrongly-licensed dependencies, find and remove dead code, audit dependency health, run and triage linters, type checkers, test suites and formatters, evaluate design principles (SOLID and the cohesion/coupling equivalents for non-OO stacks), audit logging and observability, find performance smells, check documentation and CI health, scaffold baseline configs for the detected stack, do a structured code review, guide a one-major-at-a-time dependency migration, fix project structure, or produce one aggregated health report across all of these. Triggers on phrases like clean this up, find security issues, remove dead code, check dependencies, lint, typecheck, run the tests, format, review my code, check the design, check logging, is this slow, migrate a dependency, fix the project structure, set up the project, audit everything, due diligence, or this looks like AI slop

2026-06-0314

llm-council

saski/augmentedcode-configuration

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

2026-05-2714

modern-cli-design

saski/augmentedcode-configuration

Principles for building Unix-composable command-line tools in Go: stdout/stderr discipline, JSON and plain output modes, semantic exit codes, noun-verb commands, structured errors. Use when designing, building, or reviewing CLIs.

2026-05-2714

name	personal-knowledge-routing
description	Route durable personal context and reusable knowledge between augmentedcode-configuration and the personal knowledge vault. Use when the user asks to remember, persist, capture, retrieve, or organize personal knowledge; when deciding whether information belongs in rules, skills, portfolio, notes, maps, or inbox; or when using personal-knowledge-vault as a low-context reference layer.

Personal Knowledge Routing

Use this skill to keep agent instructions small while preserving durable knowledge in the personal knowledge vault.

Repositories

Agent configuration: /Users/saski/Code/augmentedcode-configuration
Personal vault: /Users/saski/Code/personal-knowledge-vault
Vault content root: /Users/saski/Code/personal-knowledge-vault/vault

First Files To Read

When working with the vault, start with:

vault/AGENT_GUIDE.md
vault/README.md
vault/_meta/conventions.md
vault/_meta/promotion-policy.md when moving content into more durable areas
vault/_meta/source-manifest.md when source material creates or changes durable content
The smallest relevant vault/maps/*.md, vault/portfolio/*.md, or vault/notes/*.md file

Do not read the whole vault unless the user explicitly asks for a full audit.

Routing Table

Information type	Destination
Agent behavior that must apply across tools	`augmentedcode-configuration/.agents/rules/`
Repeatable agent workflow or protocol	`augmentedcode-configuration/.agents/skills/`
Tool setup, symlink policy, validation scripts	`augmentedcode-configuration/`
Stable personal facts, preferences, goals, responsibilities, working agreements	`personal-knowledge-vault/vault/portfolio/`
Durable decisions and decision-making patterns	`personal-knowledge-vault/vault/portfolio/decision-log.md` or `vault/notes/`
Distilled reusable knowledge, source summaries, lessons, patterns	`personal-knowledge-vault/vault/notes/`
Navigation and topic indexes	`personal-knowledge-vault/vault/maps/`
Raw imports, unprocessed conversations, temporary captures	`personal-knowledge-vault/vault/inbox/`
Source provenance and promotion decisions	`personal-knowledge-vault/vault/_meta/source-manifest.md` and `vault/_meta/promotion-policy.md`
Vault schema, conventions, and maintenance policy	`personal-knowledge-vault/vault/_meta/`

Persistence Rules

Prefer references over copying: if the vault already contains the knowledge, link or cite the file path instead of pasting it into rules.
Update portfolio/ only when information is stable, reusable, and source-backed.
Apply the vault promotion policy before moving content from inbox/ to notes/ or from notes/ to portfolio/.
Update the source manifest when a source creates or changes durable notes, portfolio context, maps, or governance files.
Put uncertain or still-evolving material in notes/ or inbox/ first.
Keep raw conversations out of portfolio/.
Preserve user-authored vault content unless the user explicitly asks for a rewrite.

Context Discipline

Use maps and frontmatter as indexes before reading full files.
Read exact target files; avoid broad recursive reads.
If a task needs personal context, load the relevant portfolio file rather than embedding that context in AGENTS.md.
If a rule starts accumulating domain knowledge, move the knowledge to the vault and leave a short routing rule here.

Link Discipline

Before writing an Obsidian wikilink, verify that the target note exists.
If the target is uncertain, write plain text or a relative Markdown path instead of creating a broken wikilink.
After vault edits, run make check from /Users/saski/Code/personal-knowledge-vault.
The vault pre-commit hook and scheduled GitHub workflow also run make check.

Good Defaults

For "remember this about me": propose a concise portfolio/ update, then apply it only if the source is stable.
For "save this idea": create or update a notes/ page and link it from a relevant maps/ page.
For "capture this conversation": put raw or summary material under inbox/ or notes/, then propose any portfolio promotion separately.
For "make agents aware": add the smallest possible rule or skill pointer in augmentedcode-configuration, with details stored in the vault.