メニュー
This skill should be used when the user asks to "check tags", "update tags", "audit tags", "change tag", "list tags", "tag this note", "fix frontmatter tags", or needs to manage tags across notes.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/JSai23/claude-tooling --skill tags-kコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
SKILL.md を表示中
SOC 職業分類に基づく
| name | tags-k |
| type | knowledge |
| description | This skill should be used when the user asks to "check tags", "update tags", "audit tags", "change tag", "list tags", "tag this note", "fix frontmatter tags", or needs to manage tags across notes. |
| argument-hint | <filepath | --audit | --list> |
Knowledge skill — Tag vocabulary and rules: the 5-tag system, design principles, lifecycle, valid combinations.
Manage the vault's intent-based tag vocabulary. Tags express the role a note plays in your thinking — orthogonal to PARA (which handles location) and type (which handles what it is).
5 tags. Each describes the note's role in your knowledge system:
| Tag | Role | When to Use |
|---|---|---|
#seed | Raw spark | Early idea, observation, unprocessed thought. Needs development. |
#thread | Developing narrative | Part of a bigger picture, connects to ongoing thinking. Being actively developed. |
#tool | Applicable method | Framework, technique, mental model, methodology. Something to apply. |
#question | Open gap | Unresolved question, gap in understanding, thing to figure out. |
#insight | Crystallized understanding | Key takeaway, "aha" moment, settled understanding. |
#seed in math-stats and a #seed in ai-dev-ecosystem both mean "needs development"status frontmatter field (draft, refining, or omitted for stable)Tags can combine: [seed, question] (a question that's still raw), [tool, insight] (a framework you've crystallized). Keep to 1-2 tags. If you need 3+, the note probably needs splitting.
Notes naturally move through tags as understanding develops:
#seed → #thread → #insight (ideas that crystallize)
#seed → #question → #insight (questions that get answered)
#tool stays #tool (methods are stable once captured)
Trigger: /tags path/to/note.md
#seed#thread#tool#question#insighttags: fieldTrigger: /tags --audit
Scan all notes and report:
tags field (exclude MOCs, project briefs)#seed older than 30 days — develop or archive#question notes — any answered? Any resolvable?Exclude _System/, .obsidian/, 04-archive/ from scan.
Trigger: /tags --list
Group all notes by tag:
## #seed (N notes)
- path/to/note.md
## #thread (N notes)
...
## #insight (N notes)
...
## #tool (N notes)
...
## #question (N notes)
...
## Untagged (N notes)
...