scope

Name: scope
Author: pariyar07

18stars2forks

How to install scope?

pariyar07/ariadne/scope

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

Installs into the current project.

Summary

Use when creating, promoting, importing, nesting, or reorganizing scopes inside an existing Markdown knowledge vault with inherited parent and child scope rules.

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Scope
2
3	Use this skill when a vault already exists and the user wants a new durable scope or child scope.
4
5	## Start
6
7	1. Read root instructions and every applicable ancestor scope instruction through the intended parent.
8	2. Read root/local indexes, agent navigation, task routing, and the parent hub.
9	3. In a multi-scope vault, require the new scope name and parent to be named or confirmed in the current turn.
10	4. Run the validator-owned `sync_scope_topology.js --check` in zero-write mode. Use [scope-operation-request.md](references/scope-operation-request.md) for the exact schema-v1 request and CLI.
11	5. If the vault is Git-backed, inspect status before writing. Preserve unrelated modified and untracked files, never use broad staging, and stage only paths in the declared write set when the user explicitly authorizes a commit.
12
13	## Minimal Questions
14
15	Ask only what is missing:
16
17	1. What is the scope name?
18	2. Where should it live?
19	3. What recurring job does it serve?
20	4. Does it need intake infrastructure — `Raw/Sources/`, `Inbox/`, `Processing Queue/`, local `Ingest Compile Workflow`?
21	5. Does it need local rules, templates, Bases, or only a hub?
22
23	## Promotion Threshold
24
25	Promote only when repeated work needs a durable route, local lifecycle, or local operating rules. A useful folder, a one-off project, or a possible future route stays a normal folder.
26
27	## Create, Adopt, Move, Or Change Status
28
29	1. Confirm the target scope and requested lifecycle action in the current turn. Audit/check is always zero-write; create, adopt, move, set-status, and repair require confirmation.
30	2. Build the exact request with `allowed_write_paths: []`. Run it to obtain the refusal/disclosure, then show every proposed `content_write_paths` entry. Generated-only checkpoints do not waive confirmation.
31	3. After confirmation, copy exactly those paths into `allowed_write_paths` and invoke `sync_scope_topology.js --write --request`. Never directly edit descriptors, generated files, generated blocks, registry/map artifacts, physical moves, parent relationships, or redirects.
32	4. For create, prepare the destination directory and user-owned content, then let the engine create the descriptor and generated wiring. Non-registry root Base formulas are report-only: the synchronizer detects missing or misordered scope branches but does not authorize or rewrite these user-authored formulas. After the engine write, update each reported Base outside generated blocks only when it is named in an explicit allowed_write_set. Insert the most-specific child branch before its parent branch; first-match formulas otherwise classify the child as its parent.
33	5. For adopt, choose `ancestor-chain` (target plus required ancestors) or `whole-vault` explicitly. Do not adopt candidates marked `ariadne_scope_adoption: dismissed`.
34	6. For move/reparent, provide the exact current `source_path` and new `destination_path`. The engine performs the physical move, reparents the subtree, records former paths, and writes the redirect; never emulate those steps manually.
35	7. For status, use only supported transitions: active to archived, archived to active or retired, and retired to archived. A retired scope cannot have active children. A replacement is valid only when retiring.
36	8. If interrupted, report the operation ID and use `--resume` or `--abort`; never manipulate engine control files. Reconcile any abort `reconciliation_paths` before another operation.
37	9. Run scoped validation first, then whole-vault validation. The scoped run must report `routing-matrix-warnings: 0` and `base-scope-formula-warnings: 0` for the subtree. Report unrelated pre-existing whole-vault warnings separately.
38	10. Run a second check with `sync_scope_topology.js --check`. It must disclose no changes; this is the idempotency checkpoint.
39	11. If the parent vault is not globally registered, or its global discovery block is stale, offer `ariadne:global-discovery` for the parent vault. Scope creation should not write global files or add scope-specific global discovery rules.
40	12. If an external code repository or folder should point to this scope, offer `ariadne:workspace-instructions`. Scope-specific workspace links require a current-turn explicit target or user confirmation and belong in workspace files, not global discovery.
41
42	## Import Existing Vault As Scope
43
44	1. Confirm target scope path.
45	2. Copy source vault into that scope path.
46	3. Preserve local instructions as local deltas.
47	4. Rewrite cross-scope links only when needed for validation or ambiguity.
48	5. Scope local Bases to the imported path.
49	6. Route adoption and generated parent/child wiring through the synchronizer workflow above.
50	7. Validate twice and require the second check to be empty.
51
52	## Rules
53
54	- Parent scope policy is inherited.
55	- Child scopes add

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

scope

18stars2forks

View on GitHub

How to install scope?

pariyar07/ariadne/scope

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

Installs into the current project.

Summary

Use when creating, promoting, importing, nesting, or reorganizing scopes inside an existing Markdown knowledge vault with inherited parent and child scope rules.

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Scope
2
3	Use this skill when a vault already exists and the user wants a new durable scope or child scope.
4
5	## Start
6
7	1. Read root instructions and every applicable ancestor scope instruction through the intended parent.
8	2. Read root/local indexes, agent navigation, task routing, and the parent hub.
9	3. In a multi-scope vault, require the new scope name and parent to be named or confirmed in the current turn.
10	4. Run the validator-owned `sync_scope_topology.js --check` in zero-write mode. Use [scope-operation-request.md](references/scope-operation-request.md) for the exact schema-v1 request and CLI.
11	5. If the vault is Git-backed, inspect status before writing. Preserve unrelated modified and untracked files, never use broad staging, and stage only paths in the declared write set when the user explicitly authorizes a commit.
12
13	## Minimal Questions
14
15	Ask only what is missing:
16
17	1. What is the scope name?
18	2. Where should it live?
19	3. What recurring job does it serve?
20	4. Does it need intake infrastructure — `Raw/Sources/`, `Inbox/`, `Processing Queue/`, local `Ingest Compile Workflow`?
21	5. Does it need local rules, templates, Bases, or only a hub?
22
23	## Promotion Threshold
24
25	Promote only when repeated work needs a durable route, local lifecycle, or local operating rules. A useful folder, a one-off project, or a possible future route stays a normal folder.
26
27	## Create, Adopt, Move, Or Change Status
28
29	1. Confirm the target scope and requested lifecycle action in the current turn. Audit/check is always zero-write; create, adopt, move, set-status, and repair require confirmation.
30	2. Build the exact request with `allowed_write_paths: []`. Run it to obtain the refusal/disclosure, then show every proposed `content_write_paths` entry. Generated-only checkpoints do not waive confirmation.
31	3. After confirmation, copy exactly those paths into `allowed_write_paths` and invoke `sync_scope_topology.js --write --request`. Never directly edit descriptors, generated files, generated blocks, registry/map artifacts, physical moves, parent relationships, or redirects.
32	4. For create, prepare the destination directory and user-owned content, then let the engine create the descriptor and generated wiring. Non-registry root Base formulas are report-only: the synchronizer detects missing or misordered scope branches but does not authorize or rewrite these user-authored formulas. After the engine write, update each reported Base outside generated blocks only when it is named in an explicit allowed_write_set. Insert the most-specific child branch before its parent branch; first-match formulas otherwise classify the child as its parent.
33	5. For adopt, choose `ancestor-chain` (target plus required ancestors) or `whole-vault` explicitly. Do not adopt candidates marked `ariadne_scope_adoption: dismissed`.
34	6. For move/reparent, provide the exact current `source_path` and new `destination_path`. The engine performs the physical move, reparents the subtree, records former paths, and writes the redirect; never emulate those steps manually.
35	7. For status, use only supported transitions: active to archived, archived to active or retired, and retired to archived. A retired scope cannot have active children. A replacement is valid only when retiring.
36	8. If interrupted, report the operation ID and use `--resume` or `--abort`; never manipulate engine control files. Reconcile any abort `reconciliation_paths` before another operation.
37	9. Run scoped validation first, then whole-vault validation. The scoped run must report `routing-matrix-warnings: 0` and `base-scope-formula-warnings: 0` for the subtree. Report unrelated pre-existing whole-vault warnings separately.
38	10. Run a second check with `sync_scope_topology.js --check`. It must disclose no changes; this is the idempotency checkpoint.
39	11. If the parent vault is not globally registered, or its global discovery block is stale, offer `ariadne:global-discovery` for the parent vault. Scope creation should not write global files or add scope-specific global discovery rules.
40	12. If an external code repository or folder should point to this scope, offer `ariadne:workspace-instructions`. Scope-specific workspace links require a current-turn explicit target or user confirmation and belong in workspace files, not global discovery.
41
42	## Import Existing Vault As Scope
43
44	1. Confirm target scope path.
45	2. Copy source vault into that scope path.
46	3. Preserve local instructions as local deltas.
47	4. Rewrite cross-scope links only when needed for validation or ambiguity.
48	5. Scope local Bases to the imported path.
49	6. Route adoption and generated parent/child wiring through the synchronizer workflow above.
50	7. Validate twice and require the second check to be empty.
51
52	## Rules
53
54	- Parent scope policy is inherited.
55	- Child scopes add

People who liked this also viewed

6 picks

Type