global-discovery

Name: global-discovery
Author: pariyar07

18stars2forks

How to install global-discovery?

pariyar07/ariadne/global-discovery

$npx -y skills add pariyar07/ariadne --skill global-discovery

Installs into the current project.

Summary

Register existing Markdown knowledge vaults for machine-level discovery so cold agents can find long-term knowledge from any workspace. Use when checking, adding, updating, repairing, or removing global vault discovery.

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Global Discovery
2
3	Use this skill when a user already has a Markdown knowledge vault created or maintained with Ariadne and wants future cold agents to find it from outside the vault. The vault may use Obsidian as a frontend, but discovery operates on filesystem paths and agent-readable entrypoints. Also use this skill to inspect, update, or repair existing global registry files and marker-managed adapter blocks when Ariadne ships newer discovery rules.
4
5	Typical requests:
6
7	- "Make this vault discoverable to agents."
8	- "Register my existing vault globally."
9	- "Make agents find my vault from anywhere."
10	- "Check whether this vault is registered."
11	- "Run Ariadne discovery doctor."
12	- "Repair Ariadne global discovery."
13	- "Update Ariadne global discovery rules."
14	- "Change my primary registered vault."
15
16	This skill manages machine-level discovery. It does not create the vault. Use `ariadne:vault` to bootstrap a new vault.
17
18	It also does not own workspace-level `AGENTS.md`, `CLAUDE.md`, or `GEMINI.md` files. Use `ariadne:workspace-instructions` when a code repository or ordinary folder needs local instruction files or a small Ariadne vault-link block.
19
20	## Core Model
21
22	The vault remains the source of truth. Global discovery only creates a small local signpost:
23
24	1. `~/.ariadne/vaults.json` - machine-readable registry.
25	2. `~/.ariadne/vaults.md` - agent-readable registry.
26	3. Optional marker-managed blocks in global agent instruction files.
27
28	The global blocks point to `~/.ariadne/vaults.md`; they should never duplicate long vault instructions. Updating an existing registration should refresh stale marker-managed blocks in place instead of adding another global block.
29
30	## Post-Discovery Routing
31
32	This skill gets agents to the right vault. It should not take over feature execution.
33
34	After a vault is selected:
35
36	- For navigation, routing, registration, or marker repair, continue with this skill.
37	- For new vault bootstrap, use `ariadne:vault`.
38	- For scope creation or promotion, use `ariadne:scope`.
39
40	Global discovery remains a signpost.
41
42	Workspace instruction files are also signposts when they connect to Ariadne. They may point agents toward registered vault discovery or a confirmed vault/scope, but they should not duplicate global discovery blocks or copy vault instructions into a repository.
43
44	## Start Workflow
45
46	1. Determine the vault path.
47	2. Confirm the path looks like an agent-readable Markdown knowledge vault by checking for `00 Global Index.md`, `00 Index.md`, another root `00 *Index.md`, `AGENTS.md`, or `Agent/00 Agent Navigation.md`.
48	3. Determine the vault name and short purpose. Infer from the detected root index when obvious; otherwise ask.
49	4. Ask which adapters to update, or use the default `codex,claude,gemini` when the user does not care.
50	5. Offer `--dry-run` when the user wants to preview changes.
51	6. Run the registration script.
52	7. Run the doctor to audit the result against `references/discovery-rules.md`.
53	8. Report the registry and adapter files touched, plus the audit attestation.
54
55	When updating an already registered vault, treat the workflow as an idempotent refresh/repair. The goal is to bring registry entries and marker-managed global blocks up to the current Ariadne discovery wording while preserving all user-maintained instructions outside Ariadne markers.
56
57	## Registration Command
58
59	Use the shared registration script from `ariadne:vault`:
60
61	```bash
62	node /path/to/skills/vault/scripts/register_vault.js \
63	--vault "/path/to/vault" \
64	--name "Vault Name" \
65	--purpose "Short purpose statement." \
66	--agents codex,claude,gemini \
67	--primary
68	```
69
70	Use `--agents none` to update only the registry files.
71
72	Use `--agents all` only when the user explicitly wants all supported adapters.
73
74	Use `--dry-run` before writing if the user is cautious or if existing global instruction files are complex.
75
76	## Check Discovery
77
78	Use `--check` or `--doctor` when the user wants to verify global discovery without changing files:
79
80	```bash
81	node /path/to/skills/vault/scripts/register_vault.js \
82	--agents codex,claude,gemini \
83	--doctor
84	```
85
86	The doctor checks:
87
88	- `~/.ariadne/vaults.json` exists and parses.
89	- `~/.ariadne/vaults.md` matches the JSON registry.
90	- registered vault paths exist.
91	- registered entrypoints exist in each vault.
92	- detected root entrypoints are registered.
93	- selected global adapter files have Ariadne marker blocks.
94	- adapter blocks point to `~/.ariadne/vaults.md` and include current discovery rules for listed cold-start entry order, action prompts, multiple vault matches, and target-scope confirmation.
95	- adapter blocks remain small signposts (block size is bounded; oversized blocks are flagged).
96	- each adapter file has exactly one discovery bloc

People who liked this also viewed

6 picks

Type

global-discovery

18stars2forks

View on GitHub

How to install global-discovery?

pariyar07/ariadne/global-discovery

$npx -y skills add pariyar07/ariadne --skill global-discovery

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Global Discovery
2
3	Use this skill when a user already has a Markdown knowledge vault created or maintained with Ariadne and wants future cold agents to find it from outside the vault. The vault may use Obsidian as a frontend, but discovery operates on filesystem paths and agent-readable entrypoints. Also use this skill to inspect, update, or repair existing global registry files and marker-managed adapter blocks when Ariadne ships newer discovery rules.
4
5	Typical requests:
6
7	- "Make this vault discoverable to agents."
8	- "Register my existing vault globally."
9	- "Make agents find my vault from anywhere."
10	- "Check whether this vault is registered."
11	- "Run Ariadne discovery doctor."
12	- "Repair Ariadne global discovery."
13	- "Update Ariadne global discovery rules."
14	- "Change my primary registered vault."
15
16	This skill manages machine-level discovery. It does not create the vault. Use `ariadne:vault` to bootstrap a new vault.
17
18	It also does not own workspace-level `AGENTS.md`, `CLAUDE.md`, or `GEMINI.md` files. Use `ariadne:workspace-instructions` when a code repository or ordinary folder needs local instruction files or a small Ariadne vault-link block.
19
20	## Core Model
21
22	The vault remains the source of truth. Global discovery only creates a small local signpost:
23
24	1. `~/.ariadne/vaults.json` - machine-readable registry.
25	2. `~/.ariadne/vaults.md` - agent-readable registry.
26	3. Optional marker-managed blocks in global agent instruction files.
27
28	The global blocks point to `~/.ariadne/vaults.md`; they should never duplicate long vault instructions. Updating an existing registration should refresh stale marker-managed blocks in place instead of adding another global block.
29
30	## Post-Discovery Routing
31
32	This skill gets agents to the right vault. It should not take over feature execution.
33
34	After a vault is selected:
35
36	- For navigation, routing, registration, or marker repair, continue with this skill.
37	- For new vault bootstrap, use `ariadne:vault`.
38	- For scope creation or promotion, use `ariadne:scope`.
39
40	Global discovery remains a signpost.
41
42	Workspace instruction files are also signposts when they connect to Ariadne. They may point agents toward registered vault discovery or a confirmed vault/scope, but they should not duplicate global discovery blocks or copy vault instructions into a repository.
43
44	## Start Workflow
45
46	1. Determine the vault path.
47	2. Confirm the path looks like an agent-readable Markdown knowledge vault by checking for `00 Global Index.md`, `00 Index.md`, another root `00 *Index.md`, `AGENTS.md`, or `Agent/00 Agent Navigation.md`.
48	3. Determine the vault name and short purpose. Infer from the detected root index when obvious; otherwise ask.
49	4. Ask which adapters to update, or use the default `codex,claude,gemini` when the user does not care.
50	5. Offer `--dry-run` when the user wants to preview changes.
51	6. Run the registration script.
52	7. Run the doctor to audit the result against `references/discovery-rules.md`.
53	8. Report the registry and adapter files touched, plus the audit attestation.
54
55	When updating an already registered vault, treat the workflow as an idempotent refresh/repair. The goal is to bring registry entries and marker-managed global blocks up to the current Ariadne discovery wording while preserving all user-maintained instructions outside Ariadne markers.
56
57	## Registration Command
58
59	Use the shared registration script from `ariadne:vault`:
60
61	```bash
62	node /path/to/skills/vault/scripts/register_vault.js \
63	--vault "/path/to/vault" \
64	--name "Vault Name" \
65	--purpose "Short purpose statement." \
66	--agents codex,claude,gemini \
67	--primary
68	```
69
70	Use `--agents none` to update only the registry files.
71
72	Use `--agents all` only when the user explicitly wants all supported adapters.
73
74	Use `--dry-run` before writing if the user is cautious or if existing global instruction files are complex.
75
76	## Check Discovery
77
78	Use `--check` or `--doctor` when the user wants to verify global discovery without changing files:
79
80	```bash
81	node /path/to/skills/vault/scripts/register_vault.js \
82	--agents codex,claude,gemini \
83	--doctor
84	```
85
86	The doctor checks:
87
88	- `~/.ariadne/vaults.json` exists and parses.
89	- `~/.ariadne/vaults.md` matches the JSON registry.
90	- registered vault paths exist.
91	- registered entrypoints exist in each vault.
92	- detected root entrypoints are registered.
93	- selected global adapter files have Ariadne marker blocks.
94	- adapter blocks point to `~/.ariadne/vaults.md` and include current discovery rules for listed cold-start entry order, action prompts, multiple vault matches, and target-scope confirmation.
95	- adapter blocks remain small signposts (block size is bounded; oversized blocks are flagged).
96	- each adapter file has exactly one discovery bloc

People who liked this also viewed

6 picks

Type