maintenance

Name: maintenance
Author: pariyar07

18stars2forks

How to install maintenance?

pariyar07/ariadne/maintenance

$npx -y skills add pariyar07/ariadne --skill maintenance

Installs into the current project.

Summary

Run maintenance and health checks for agent-maintained Markdown knowledge vaults: broken links, orphan notes, stale hubs, invalid frontmatter, uncompiled raw sources, stale queues, unresolved questions, optional Base coverage, and health reports.

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Maintenance
2
3	Use this skill when auditing, repairing, or maintaining a Markdown knowledge vault over time.
4
5	## Start
6
7	1. Read root instructions and every applicable ancestor scope instruction through the target.
8	2. Read relevant indexes, agent navigation, health-check procedure, and navigation standard.
9	3. Discover findings read-only. In a multi-scope vault, require a current-turn named or confirmed target before scoped repairs.
10	4. Run `sync_scope_topology.js --check` for topology findings. Audit/check behavior is always zero-write.
11
12	## Health Checks
13
14	Check for:
15
16	- invalid Markdown frontmatter
17	- invalid `.base` YAML
18	- broken wikilinks, resolving both `.md` and `.base` files
19	- Markdown notes with no incoming or outgoing wikilinks
20	- `.base` files missing from `Bases/00 Bases Index.md`
21	- important notes missing from folder hubs
22	- folder hubs missing from agent navigation
23	- stale inbox items
24	- stale processing queue items
25	- decisions without rationale
26	- generated outputs that should be filed back into the wiki
27	- entry files or folder hubs becoming too large to scan
28	- durable folders without `00 ... Index.md` hubs
29	- recurring workstreams missing from task routing
30	- stale or missing local `AGENTS.md` files for specialized folders
31	- promoted scopes missing hubs
32	- child hubs missing parent links
33	- parent hubs missing child links
34	- local Bases missing folder scope filters
35	- local `AGENTS.md` files repeating parent policy instead of local deltas
36	- local queues piling up inside child scopes
37	- scope indexes becoming full tables of contents instead of navigable maps
38
39	## Proactive Repair Routing
40
41	When you discover a problem during unrelated vault work, surface it instead of letting it become hidden drift:
42
43	1. State what appears broken.
44	2. Explain why it matters for future agents or human navigation.
45	3. Recommend the smallest next check or skill.
46	4. Say whether you can safely fix it now or need approval.
47
48	Use this routing:
49
50	- Global discovery, stale registry entrypoints, or missing adapter marker blocks: use `ariadne:global-discovery` and run the Ariadne discovery doctor.
51	- Broken wikilinks, orphan notes, invalid frontmatter, invalid `.base` YAML, unlinked Bases, or validator warnings: use `ariadne:validator` first, then repair with this skill.
52	- Navigation bloat, missing hubs, missing parent-child hub links, task routing drift, or unclear scope boundaries: use `ariadne:navigation`.
53	- General inbox, processing, or output buildup: use `ariadne:knowledge-capture`.
54	- Research provenance, compilation coverage, stale synthesis, unresolved research questions, evidence roles, circular corroboration, or older pipeline drift: use `ariadne:research-stewardship`.
55	- Missing repeatable research infrastructure inside a scope: use `ariadne:research-pipeline`.
56
57	Whole-vault maintenance discovers and routes research-semantic drift; it does not reproduce the research stewardship procedure or make synthesis dispositions.
58
59	Keep the repair scoped to the nearest responsible folder or domain. Ask before restructuring navigation, modifying global agent files, or installing/updating skills.
60
61	## Scope Candidate And Repair Ownership
62
63	- Inventory evidence before recommending promotion: recurring routing need, durable local lifecycle, local policy, repeated local views, and current parent route.
64	- Respect `ariadne_scope_adoption: dismissed`; do not repeatedly propose or silently adopt a dismissed candidate.
65	- For an approved adoption, offer `ancestor-chain` (the target and required ancestors) versus `whole-vault` (all supported pending descriptors), explain the difference, and require a current-turn choice.
66	- Cleanup recommendations must cite findings and paths. Never infer deletion, retirement, relocation, or normalization from an unused-looking folder alone.
67	- Topology repairs require a confirmed target and disclosed `allowed_write_paths`. Route them through the validator-owned `sync_scope_topology.js`; never directly edit descriptors, generated blocks/files, root scope formulas, redirects, or scope moves.
68	- After an approved repair, run scoped and whole-vault validation and a second zero-change check. Use `--resume` or `--abort` for interrupted operations and reconcile reported paths.
69
70	## Report
71
72	Report findings in the chat or automation output by default.
73
74	Save dated reports in `Outputs/` using the vault's health-check template when the user asks for a durable health record, the vault's local procedure requires it, or unresolved follow-ups need a durable note. Do not create recurring report notes just because a scheduled automation ran.
75
76	Use statuses such as:
77
78	- `healthy`
79	- `needs-review`
80	- `needs-linking`
81	- `needs-compilation`
82	- `needs-decision`

People who liked this also viewed

6 picks

Type

maintenance

18stars2forks

View on GitHub

How to install maintenance?

pariyar07/ariadne/maintenance

$npx -y skills add pariyar07/ariadne --skill maintenance

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Maintenance
2
3	Use this skill when auditing, repairing, or maintaining a Markdown knowledge vault over time.
4
5	## Start
6
7	1. Read root instructions and every applicable ancestor scope instruction through the target.
8	2. Read relevant indexes, agent navigation, health-check procedure, and navigation standard.
9	3. Discover findings read-only. In a multi-scope vault, require a current-turn named or confirmed target before scoped repairs.
10	4. Run `sync_scope_topology.js --check` for topology findings. Audit/check behavior is always zero-write.
11
12	## Health Checks
13
14	Check for:
15
16	- invalid Markdown frontmatter
17	- invalid `.base` YAML
18	- broken wikilinks, resolving both `.md` and `.base` files
19	- Markdown notes with no incoming or outgoing wikilinks
20	- `.base` files missing from `Bases/00 Bases Index.md`
21	- important notes missing from folder hubs
22	- folder hubs missing from agent navigation
23	- stale inbox items
24	- stale processing queue items
25	- decisions without rationale
26	- generated outputs that should be filed back into the wiki
27	- entry files or folder hubs becoming too large to scan
28	- durable folders without `00 ... Index.md` hubs
29	- recurring workstreams missing from task routing
30	- stale or missing local `AGENTS.md` files for specialized folders
31	- promoted scopes missing hubs
32	- child hubs missing parent links
33	- parent hubs missing child links
34	- local Bases missing folder scope filters
35	- local `AGENTS.md` files repeating parent policy instead of local deltas
36	- local queues piling up inside child scopes
37	- scope indexes becoming full tables of contents instead of navigable maps
38
39	## Proactive Repair Routing
40
41	When you discover a problem during unrelated vault work, surface it instead of letting it become hidden drift:
42
43	1. State what appears broken.
44	2. Explain why it matters for future agents or human navigation.
45	3. Recommend the smallest next check or skill.
46	4. Say whether you can safely fix it now or need approval.
47
48	Use this routing:
49
50	- Global discovery, stale registry entrypoints, or missing adapter marker blocks: use `ariadne:global-discovery` and run the Ariadne discovery doctor.
51	- Broken wikilinks, orphan notes, invalid frontmatter, invalid `.base` YAML, unlinked Bases, or validator warnings: use `ariadne:validator` first, then repair with this skill.
52	- Navigation bloat, missing hubs, missing parent-child hub links, task routing drift, or unclear scope boundaries: use `ariadne:navigation`.
53	- General inbox, processing, or output buildup: use `ariadne:knowledge-capture`.
54	- Research provenance, compilation coverage, stale synthesis, unresolved research questions, evidence roles, circular corroboration, or older pipeline drift: use `ariadne:research-stewardship`.
55	- Missing repeatable research infrastructure inside a scope: use `ariadne:research-pipeline`.
56
57	Whole-vault maintenance discovers and routes research-semantic drift; it does not reproduce the research stewardship procedure or make synthesis dispositions.
58
59	Keep the repair scoped to the nearest responsible folder or domain. Ask before restructuring navigation, modifying global agent files, or installing/updating skills.
60
61	## Scope Candidate And Repair Ownership
62
63	- Inventory evidence before recommending promotion: recurring routing need, durable local lifecycle, local policy, repeated local views, and current parent route.
64	- Respect `ariadne_scope_adoption: dismissed`; do not repeatedly propose or silently adopt a dismissed candidate.
65	- For an approved adoption, offer `ancestor-chain` (the target and required ancestors) versus `whole-vault` (all supported pending descriptors), explain the difference, and require a current-turn choice.
66	- Cleanup recommendations must cite findings and paths. Never infer deletion, retirement, relocation, or normalization from an unused-looking folder alone.
67	- Topology repairs require a confirmed target and disclosed `allowed_write_paths`. Route them through the validator-owned `sync_scope_topology.js`; never directly edit descriptors, generated blocks/files, root scope formulas, redirects, or scope moves.
68	- After an approved repair, run scoped and whole-vault validation and a second zero-change check. Use `--resume` or `--abort` for interrupted operations and reconcile reported paths.
69
70	## Report
71
72	Report findings in the chat or automation output by default.
73
74	Save dated reports in `Outputs/` using the vault's health-check template when the user asks for a durable health record, the vault's local procedure requires it, or unresolved follow-ups need a durable note. Do not create recurring report notes just because a scheduled automation ran.
75
76	Use statuses such as:
77
78	- `healthy`
79	- `needs-review`
80	- `needs-linking`
81	- `needs-compilation`
82	- `needs-decision`

People who liked this also viewed

6 picks

Type