knowledge-capture

Name: knowledge-capture
Author: pariyar07

18stars2forks

How to install knowledge-capture?

pariyar07/ariadne/knowledge-capture

$npx -y skills add pariyar07/ariadne --skill knowledge-capture

Installs into the current project.

Summary

Use when links, documents, PDFs, transcripts, screenshots, meeting notes, observations, brain dumps, or other material must be compiled into an explicitly selected Markdown knowledge-vault destination.

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Knowledge Capture
2
3	Compile material after its destination and write set are known. This skill does not select a research scope, create research topology, classify evidence independently, or judge synthesis disposition.
4
5	## Authorization
6
7	1. Require a known destination and explicit `allowed_write_set` before writing. In a multi-scope vault, the target must be named or confirmed in the current turn.
8	2. Read root instructions and every ancestor scope instruction through the target.
9	3. Read relevant indexes, agent navigation, routing, local ingest workflow, and folder hubs progressively.
10	4. Keep every mutation inside the write set. Parent/root navigation, sibling scopes, and downstream destinations require individually named paths.
11
12	For research, consume the full `ariadne:research-ingest` handoff envelope without changing it:
13
14	```text
15	target_scope
16	research_boundary
17	allowed_write_set
18	source_type
19	evidence_role
20	derived_from
21	inquiry_links
22	pipeline_state
23	requested_operation
24	```
25
26	If a research envelope is missing, ambiguous, or requests paths outside the set, return to `ariadne:research-ingest`. Route missing topology to `ariadne:research-pipeline` rather than creating it silently.
27
28	## Capture And Compile
29
30	1. Capture one canonical raw artifact when the source must remain inspectable. For research, preserve `source_type`, `evidence_role`, `derived_from`, and `research_boundary` exactly from the handoff. Map handoff `inquiry_links` to artifact field `inquiries`; use an empty flat list when no inquiry is known.
31	2. Separate observed or source claims from interpretation.
32	3. Compile the smallest durable note or notes supported by the material.
33	4. For compiled research, map handoff `inquiry_links` to canonical frontmatter field `inquiries` without inventing an inquiry, and link artifacts downstream to upstream with `derived_from`.
34	5. Link artifacts from authorized local hubs. Report any out-of-set navigation obligation instead of expanding scope.
35	6. Add follow-up items only inside the allowed write set.
36	7. If compiled research may affect current understanding, hand it to `ariadne:research-synthesis`. This skill does not judge synthesis disposition.
37
38	Generated analysis and derivative copies retain upstream provenance and do not count as independent corroboration. Capture cross-scope material once; do not duplicate raw evidence.
39
40	### Minimum Research Raw Schema
41
42	Write research raw artifacts with at least this flat schema, plus local title, origin, locator, and date fields required by ancestor instructions:
43
44	```yaml
45	type: raw-source
46	research_boundary: "[[Domains/Example/Research/00 Example Research Boundary]]"
47	source_type: meeting
48	evidence_role: first-party-evidence
49	origin: Product interview
50	locator: not-applicable
51	captured: 2026-07-15
52	compilation_status: pending
53	derived_from: []
54	inquiries: []
55	```
56
57	Allowed compilation states are `pending`, `compiled`, `source-only`, or `needs-review`. Use `compiled` only when at least one derived note links back to the raw artifact. Do not change the handoff classification merely to satisfy a local template.
58
59	## Promotion Writes
60
61	Accept a promotion candidate from `ariadne:research-synthesis` only when its destination is named or confirmed in the current turn and included in the write set. Create or update the destination note with `research_basis` or equivalent `derived_from` links. Do not move, duplicate, or silently rewrite the canonical research.
62
63	## Validation
64
65	Before finishing, confirm that every write was authorized, raw material is compiled or intentionally source-only, provenance is present, claims and interpretation remain distinct, important artifacts are locally discoverable, and focused validation passes or its warnings are reported.
66
67	Use `ariadne:research-ingest` for research target resolution and classification, `ariadne:research-pipeline` for topology, `ariadne:research-synthesis` for dispositions, `ariadne:navigation` for separately authorized structural routes, and `ariadne:maintenance` for broad vault health.

People who liked this also viewed

6 picks

Type

knowledge-capture

18stars2forks

View on GitHub

How to install knowledge-capture?

pariyar07/ariadne/knowledge-capture

$npx -y skills add pariyar07/ariadne --skill knowledge-capture

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Knowledge Capture
2
3	Compile material after its destination and write set are known. This skill does not select a research scope, create research topology, classify evidence independently, or judge synthesis disposition.
4
5	## Authorization
6
7	1. Require a known destination and explicit `allowed_write_set` before writing. In a multi-scope vault, the target must be named or confirmed in the current turn.
8	2. Read root instructions and every ancestor scope instruction through the target.
9	3. Read relevant indexes, agent navigation, routing, local ingest workflow, and folder hubs progressively.
10	4. Keep every mutation inside the write set. Parent/root navigation, sibling scopes, and downstream destinations require individually named paths.
11
12	For research, consume the full `ariadne:research-ingest` handoff envelope without changing it:
13
14	```text
15	target_scope
16	research_boundary
17	allowed_write_set
18	source_type
19	evidence_role
20	derived_from
21	inquiry_links
22	pipeline_state
23	requested_operation
24	```
25
26	If a research envelope is missing, ambiguous, or requests paths outside the set, return to `ariadne:research-ingest`. Route missing topology to `ariadne:research-pipeline` rather than creating it silently.
27
28	## Capture And Compile
29
30	1. Capture one canonical raw artifact when the source must remain inspectable. For research, preserve `source_type`, `evidence_role`, `derived_from`, and `research_boundary` exactly from the handoff. Map handoff `inquiry_links` to artifact field `inquiries`; use an empty flat list when no inquiry is known.
31	2. Separate observed or source claims from interpretation.
32	3. Compile the smallest durable note or notes supported by the material.
33	4. For compiled research, map handoff `inquiry_links` to canonical frontmatter field `inquiries` without inventing an inquiry, and link artifacts downstream to upstream with `derived_from`.
34	5. Link artifacts from authorized local hubs. Report any out-of-set navigation obligation instead of expanding scope.
35	6. Add follow-up items only inside the allowed write set.
36	7. If compiled research may affect current understanding, hand it to `ariadne:research-synthesis`. This skill does not judge synthesis disposition.
37
38	Generated analysis and derivative copies retain upstream provenance and do not count as independent corroboration. Capture cross-scope material once; do not duplicate raw evidence.
39
40	### Minimum Research Raw Schema
41
42	Write research raw artifacts with at least this flat schema, plus local title, origin, locator, and date fields required by ancestor instructions:
43
44	```yaml
45	type: raw-source
46	research_boundary: "[[Domains/Example/Research/00 Example Research Boundary]]"
47	source_type: meeting
48	evidence_role: first-party-evidence
49	origin: Product interview
50	locator: not-applicable
51	captured: 2026-07-15
52	compilation_status: pending
53	derived_from: []
54	inquiries: []
55	```
56
57	Allowed compilation states are `pending`, `compiled`, `source-only`, or `needs-review`. Use `compiled` only when at least one derived note links back to the raw artifact. Do not change the handoff classification merely to satisfy a local template.
58
59	## Promotion Writes
60
61	Accept a promotion candidate from `ariadne:research-synthesis` only when its destination is named or confirmed in the current turn and included in the write set. Create or update the destination note with `research_basis` or equivalent `derived_from` links. Do not move, duplicate, or silently rewrite the canonical research.
62
63	## Validation
64
65	Before finishing, confirm that every write was authorized, raw material is compiled or intentionally source-only, provenance is present, claims and interpretation remain distinct, important artifacts are locally discoverable, and focused validation passes or its warnings are reported.
66
67	Use `ariadne:research-ingest` for research target resolution and classification, `ariadne:research-pipeline` for topology, `ariadne:research-synthesis` for dispositions, `ariadne:navigation` for separately authorized structural routes, and `ariadne:maintenance` for broad vault health.

People who liked this also viewed

6 picks

Type