skillwiki 0.2.1-beta.3 → 0.2.1-beta.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "skillwiki",
|
|
3
|
-
"version": "0.2.1-beta.
|
|
3
|
+
"version": "0.2.1-beta.4",
|
|
4
4
|
"skills": "./",
|
|
5
5
|
"description": "Project-aware Karpathy-style knowledge base for Claude Code: 15 prompt-only skills (wiki-*, proj-*, using-skillwiki) backed by the deterministic `skillwiki` CLI.",
|
|
6
6
|
"author": {
|
package/skills/package.json
CHANGED
|
@@ -55,6 +55,14 @@ sha256: # computed by skillwiki hash over body bytes after closing ---
|
|
|
55
55
|
|
|
56
56
|
**No `inbox/` directory.** Ad-hoc captures go to `raw/transcripts/` or directly into a project work item via `proj-work`. Do not invent new top-level directories — extend Layer 2 via SCHEMA.md tag taxonomy if needed.
|
|
57
57
|
|
|
58
|
+
### Ad-hoc capture: three entry points
|
|
59
|
+
|
|
60
|
+
| Entry | When | What happens |
|
|
61
|
+
|-------|------|-------------|
|
|
62
|
+
| `/wiki-add-task <text>` | You're in a Claude session | Appends entry to `raw/transcripts/YYYY-MM-DD-ad-hoc-captures.md` |
|
|
63
|
+
| Filesystem drop | You're NOT in a Claude session (Obsidian, editor, sync) | Create/edit any `.md` file in `raw/transcripts/` — dev-loop discovers it on next cycle |
|
|
64
|
+
| Dev-loop discovery | Automatic, next cycle | Scans `raw/transcripts/` for new files since last cycle, surfaces as claimable work |
|
|
65
|
+
|
|
58
66
|
## Skill Map
|
|
59
67
|
|
|
60
68
|
| Skill | When to Invoke |
|
|
@@ -1,15 +1,21 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: wiki-add-task
|
|
3
|
-
description: Capture ad-hoc ideas, bugs, tasks, or notes into the vault
|
|
3
|
+
description: Capture ad-hoc ideas, bugs, tasks, or notes into the vault via /wiki-add-task or filesystem drop.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# wiki-add-task
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
Capture ad-hoc ideas, bugs, tasks, and notes into the vault. Three entry points depending on where you are:
|
|
9
|
+
|
|
10
|
+
| Entry | When | What happens |
|
|
11
|
+
|-------|------|-------------|
|
|
12
|
+
| `/wiki-add-task <text>` | You're in a Claude session | Appends entry to `raw/transcripts/YYYY-MM-DD-ad-hoc-captures.md` |
|
|
13
|
+
| Filesystem drop | You're NOT in a Claude session (Obsidian, editor, sync) | Create/edit any file in `raw/transcripts/` — dev-loop discovers it on next cycle |
|
|
14
|
+
| Dev-loop discovery | Automatic, next cycle | Scans `raw/transcripts/` for new files since last cycle, surfaces as claimable work |
|
|
9
15
|
|
|
10
16
|
## When This Skill Activates
|
|
11
17
|
|
|
12
|
-
- User
|
|
18
|
+
- User invokes `/wiki-add-task` with a description.
|
|
13
19
|
- User says "add task", "capture this", "note this", "remember this", "log this idea", or similar.
|
|
14
20
|
- User provides a short text description and optionally a type tag.
|
|
15
21
|
|
|
@@ -72,3 +78,27 @@ The `sha256` is computed over the body after the closing `---`. On each append,
|
|
|
72
78
|
- Modifying existing entries in the captures file — only append.
|
|
73
79
|
- Creating a work item — this is capture-only. Use `proj-work` for full work items.
|
|
74
80
|
- Writing to any Layer 2 or Layer 3 location. Captures are Layer 1 (raw).
|
|
81
|
+
|
|
82
|
+
## Filesystem drop (offline capture)
|
|
83
|
+
|
|
84
|
+
When you're not in a Claude session, drop files directly into `raw/transcripts/`:
|
|
85
|
+
|
|
86
|
+
1. Create any `.md` file in `raw/transcripts/` — name it descriptively (e.g., `2026-05-07-idea-xyz.md`)
|
|
87
|
+
2. Add raw frontmatter at the top:
|
|
88
|
+
```yaml
|
|
89
|
+
---
|
|
90
|
+
source_url:
|
|
91
|
+
ingested: YYYY-MM-DD
|
|
92
|
+
sha256:
|
|
93
|
+
---
|
|
94
|
+
```
|
|
95
|
+
3. Write your idea/bug/task/note below the frontmatter
|
|
96
|
+
|
|
97
|
+
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.
|
|
98
|
+
|
|
99
|
+
## Dev-loop discovery
|
|
100
|
+
|
|
101
|
+
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:
|
|
102
|
+
- Create a work item via `proj-work` (for tasks and bugs)
|
|
103
|
+
- Ingest as a knowledge page via `wiki-ingest` (for ideas with sources)
|
|
104
|
+
- Leave in place (for notes that don't need action yet)
|