SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillswiki-add-task

wiki-add-task

General & other

View repository

Updated 10-15 23:44

About this skill

wiki-add-task

Capture ad-hoc ideas, bugs, tasks, and notes into the vault. Three entry points depending on where you are:

Entry When What happens
/wiki-add-task <text> You're in a Claude Code session (NOT Hermes compact) Creates raw/transcripts/YYYY-MM-DD-{type}-{slug}.md with ad-hoc capture frontmatter
Filesystem drop Hermes Agent compact mode (no slash commands available) Same as above — create .md in raw/transcripts/, dev-loop discovers it
Filesystem drop You're NOT in a Claude session (Obsidian, editor, sync) Create any .md file in raw/transcripts/ using the vault template — dev-loop discovers it on next cycle
Dev-loop discovery Automatic, next cycle Scans raw/transcripts/ for new files since last cycle, surfaces as claimable work
Path Rule: Captures ALWAYS go to $(skillwiki path)/raw/transcripts/ (Layer 1). Never under projects/{slug}/raw/ — that violates SCHEMA.md Layer 1 immutability.

Exception: Explicit project task requests

When the user explicitly says "raise task to project X", "add a task for X", "create a feature request for X", or uses a directive structure like "raise task to {project} {description}", the intent is a work item, not a capture:

User wording Action Target
"capture this", "note this", "remember this" Use wiki-add-task (this skill) raw/transcripts/
"raise task to project X", "add task to X project" Escalate to proj-work projects/{slug}/work/YYYY-MM-DD-{slug}/task.md
"save to wiki" + content Use wiki-ingest concepts/, entities/, etc.
This is NOT a violation of the "ALWAYS" rule below — explicit project task requests are a distinct user intent that bypasses raw capture and goes directly to a Layer 3 work item.

When This Skill Activates

  • User invokes /wiki-add-task with a description.
  • User says "add task", "capture this", "note this", "remember this", "log this idea", or similar.
  • User provides a short text description and optionally a type tag.
  • Do NOT activate when the user says "raise task to project X" or "add work item to project X" — escalate to proj-work instead.

Output language

Run skillwiki lang at the start. Entry prose and --human summaries use the resolved language. Frontmatter keys, file names, and structural markers stay English.

Steps

  1. Resolve vault and language. Run skillwiki path (fail if NO_VAULT_CONFIGURED) and skillwiki lang.
  2. Parse arguments. Extract from the user's message:
  • text — the idea/bug/task/note content (required)
  • type — one of: idea, bug, task, note (default: idea)
  • project — optional project slug to cross-reference (e.g., llm-wiki)
  1. Sensitive content guard. Before writing a capture, scan the text for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact before writing. If the source text itself contains a live secret that must be preserved verbatim, STOP instead of filing it.
  2. Build filename. Derive a slug from the first ~6 words of the text (lowercased, hyphens for spaces, non-alphanumeric stripped). The capture file is raw/transcripts/YYYY-MM-DD-{type}-{slug}.md. Each capture gets its own file — never append to an existing file.
  3. Write frontmatter. Create the file with ad-hoc capture frontmatter:
---
source_url:
ingested: YYYY-MM-DD
kind: {type}
project: "[[{slug}]]"
---
  • Set kind to the parsed type (idea, bug, task, note).
  • If a project slug was provided, set project: "[[slug]]".
  • If no project, omit the project field entirely.
  • source_url is null (these are locally originated captures).
  • No sha256 — ad-hoc captures are mutable working notes, not immutable sources.
  1. Write body. Below the frontmatter, write:
# {type}: {text}
{text}

Use the resolved output language for any prose. The type label and frontmatter stay English. 6. Cross-reference (optional). If a project slug was provided:

  • Check that projects/{slug}/ exists in the vault.
  • Append a one-line reference to the project's compound notes: - [YYYY-MM-DD] capture: [text (first 60 chars)] → raw/transcripts/YYYY-MM-DD-{type}-{slug}.md
  • Do NOT create a full work item (that's proj-work's job).
  1. Update log.md. Append: ## [YYYY-MM-DD] capture | [type]: [text (first 60 chars)]
  2. Confirm to user. Report what was captured and where. Suggest next steps:
  • If type: idea → "Consider ingesting related sources to develop this idea."
  • If type: bug → "Use proj-work to create a bug-fix work item."
  • If type: task → "Use proj-work to track this task through the dev loop."
  • If type: note → "Will be available for future wiki-query searches."

Capture file format

Each capture is a standalone file with ad-hoc capture frontmatter:

---
source_url:
ingested: 2026-05-08
kind: idea
project: "[[llm-wiki]]"
---
# idea: Fix the template mismatch
Fix the template mismatch between wiki-add-task and the vault template.

The kind field uses the capture type and must be one of: idea, bug, task, note (plus the existing postmortem, session-log, meeting-notes, other for non-capture raw sources). The project and kind fields can be set independently — they do not require work_item. The work_item field is only used when the raw source is directly tied to a project work item (set by proj-work). Ad-hoc captures omit sha256 — they are mutable working notes, not immutable sources. The sha256 field is reserved for ingested raw sources that require integrity verification.

Stop conditions

  • skillwiki path returns NO_VAULT_CONFIGURED.
  • No text provided (prompt user once, then stop).
  • Target file already exists (use a different slug or add a suffix).
  • Capture text contains unredacted live credentials or other authenticating secrets.

Forbidden

  • Creating an inbox/ directory. All captures go to raw/transcripts/.
  • Appending to existing capture files — each capture gets its own file.
  • Creating a work item — this is capture-only. Use proj-work for full work items.
  • Writing to any Layer 2 or Layer 3 location. Captures are Layer 1 (raw).
  • Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault.

Filesystem drop (offline capture)

When you're not in a Claude session, drop files directly into raw/transcripts/:

  1. Create a .md file in raw/transcripts/ — name it descriptively (e.g., 2026-05-08-idea-fix-template.md)
  2. Use ad-hoc capture frontmatter: source_url:, ingested:, kind:, and optionally project:
  3. Write your idea/bug/task/note below the frontmatter No special format required — the dev-loop QUERY step will discover new files on the next cycle and surface them as claimable work. Mark the type with a heading like ## idea, ## bug, ## task, or just write freeform.

Dev-loop discovery

When the dev-loop QUERY step runs, it should scan raw/transcripts/ for files with ingested: date newer than the last cycle. New files are surfaced as claimable work items. The agent then decides whether to:

  • Create a work item via proj-work (for tasks and bugs)
  • Ingest as a knowledge page via wiki-ingest (for ideas with sources)
  • Leave in place (for notes that don't need action yet)