Skip to content

Commit 2328e4e

Browse files
baum777baum777
committed
Add organoid repo-specific skill library
1 parent 9797e3f commit 2328e4e

15 files changed

Lines changed: 848 additions & 0 deletions

File tree

‎skills/repo-specific/organoid-symbionts/README.md‎

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# organoid_Symbionts Skill Library
2+
3+
This library was derived from the local `organoid_Symbionts` repo by reading the root README, `package.json`, `render.yaml`, the runtime entrypoints, health and observability code, prompt assets, state store code, tests, and the operator docs under `docs/`.
4+
5+
## Branch Structure
6+
7+
### 1. Render Deploy Branch
8+
9+
This branch exists because the repo has a real multi-service Render blueprint:
10+
11+
- worker
12+
- health web service
13+
- landing app
14+
- daily cron
15+
16+
The Render branch holds the deploy-topology, env-contract, readiness, and rollback skills.
17+
18+
### 2. Runtime Control Branch
19+
20+
This branch covers the worker loop, fail-closed write policy, health and metrics, and durable state handling.
21+
22+
### 3. Prompt, Embodiment, and Signal Branch
23+
24+
This branch covers the canonical prompt fragments, embodiment routing, timeline engagement policy, and external read paths.
25+
26+
### 4. Validation and Derived Artifacts Branch
27+
28+
This branch covers testing, compliance, and semantic artifact regeneration so the runtime stays reproducible.
29+
30+
## Top Starter Skills
31+
32+
1. `render-blueprint-review`
33+
2. `fail-closed-write-policy-review`
34+
3. `health-and-metrics-review`
35+
4. `testing-and-compliance-gates-review`
36+
5. `prompt-canon-and-embodiment-review`
37+
38+
## Inferred Areas
39+
40+
- The lore layer is real, but the skill set treats it as an operational prompt and embodiment surface instead of assuming extra hidden runtime behavior.
41+
- The semantic build and snippet extraction flows are real, but they are treated as derived-artifact maintenance, not as a separate product model.
42+
43+
## Why Render Got Its Own Branch
44+
45+
The deploy model is visible in `render.yaml`, and it matters operationally:
46+
47+
- worker and web health run separately
48+
- landing is isolated from the worker runtime
49+
- a cron job exists alongside the always-on services
50+
- env variables differ by service
51+
52+
That is enough topology complexity to justify a dedicated branch rather than burying deploy review inside a generic ops skill.
53+

‎skills/repo-specific/organoid-symbionts/skill-tree.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# organoid_Symbionts Skill Tree
2+
3+
## Render Deploy Branch
4+
5+
- `render-blueprint-review` - reviews the Render service graph, commands, and service split
6+
- `render-env-contract-validation` - validates env vars against the runtime and Render blueprint
7+
- `render-topology-and-separation-review` - checks worker, health, landing, and cron separation
8+
- `render-readiness-and-rollback` - checks deploy readiness, runbook coverage, and rollback posture
9+
10+
## Runtime Control Branch
11+
12+
- `worker-loop-operability-review` - reviews the poller loop, launch gates, and worker entrypoint
13+
- `fail-closed-write-policy-review` - reviews approval-gated writes, public guards, and safety gates
14+
- `health-and-metrics-review` - reviews health endpoints, glyph surfaces, and Prometheus-style metrics
15+
- `state-store-and-migration-review` - reviews state store contracts and migration discipline
16+
17+
## Prompt, Embodiment, and Signal Branch
18+
19+
- `prompt-canon-and-embodiment-review` - reviews prompt assets, embodiment fragments, and lore canon
20+
- `timeline-engagement-policy-review` - reviews timeline engagement thresholds and candidate policy
21+
- `external-signal-and-verification-review` - reviews market/onchain read paths and trust boundaries
22+
23+
## Validation and Derived Artifacts Branch
24+
25+
- `testing-and-compliance-gates-review` - reviews CI, simulation, and operator-facing validation gates
26+
- `semantic-regeneration-review` - reviews semantic index rebuilds and snippet extraction artifacts
27+

‎skills/repo-specific/organoid-symbionts/skills/external-signal-and-verification-review/SKILL.md‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
name: external-signal-and-verification-review
3+
description: Reviews market and onchain read paths plus truth-resolution boundaries in organoid_Symbionts.
4+
version: 1.0.0
5+
repo: organoid_Symbionts
6+
classification: repo-specific
7+
safe_to_auto_run: true
8+
requires_repo_inputs: false
9+
produces_structured_output: true
10+
---
11+
12+
## Purpose
13+
Check that external signal ingestion stays read-focused, minimally trusted, and aligned with the repo's verification boundary.
14+
15+
## Trigger
16+
Use when market adapters, onchain adapters, or truth resolution logic changes.
17+
18+
## When to use
19+
- Reviewing adapter behavior before it reaches the runtime
20+
- Auditing truth or identity verification logic
21+
- Checking the boundary between external data and runtime decisioning
22+
23+
## When not to use
24+
- Pure local state changes
25+
- Render topology work
26+
27+
## Required inputs
28+
- `src/adapters/market/*`
29+
- `src/adapters/onchain/*`
30+
- `src/tools/marketTool.ts`
31+
- `src/tools/onchainTool.ts`
32+
- `src/truth/*`
33+
- `src/identity/*`
34+
35+
## Workflow
36+
1. Trace the external signal from adapter to downstream consumer.
37+
2. Check whether any path can mutate state or publish without explicit approval.
38+
3. Review sanitization, truth checks, and fallback behavior.
39+
4. Identify any trust assumptions that are not directly coded.
40+
41+
## Expected outputs
42+
- SUMMARY
43+
- FINDINGS
44+
- RISKS
45+
- BOUNDARIES
46+
- NEXT ACTIONS
47+
48+
## Quality checks
49+
- Adapter paths stay read-focused unless explicitly gated
50+
- Verification logic does not silently trust upstream data
51+
- Sanitizers and truth gates are applied before use
52+
53+
## Repo grounding notes
54+
- `src/adapters/market/dexscreenerAdapter.ts`
55+
- `src/adapters/market/geckoAdapter.ts`
56+
- `src/adapters/onchain/solanaRpcAdapter.ts`
57+
- `src/tools/marketTool.ts`
58+
- `src/tools/onchainTool.ts`
59+
- `src/truth/truthGate.ts`
60+
- `src/identity/onchainVerify.ts`
61+

‎skills/repo-specific/organoid-symbionts/skills/fail-closed-write-policy-review/SKILL.md‎

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
name: fail-closed-write-policy-review
3+
description: Reviews approval-gated write behavior, public guards, and safety checks for organoid_Symbionts.
4+
version: 1.0.0
5+
repo: organoid_Symbionts
6+
classification: repo-specific
7+
safe_to_auto_run: true
8+
requires_repo_inputs: false
9+
produces_structured_output: true
10+
---
11+
12+
## Purpose
13+
Verify that any outbound write path remains approval-gated, conservative, and aligned with the repo's public and safety boundaries.
14+
15+
## Trigger
16+
Use when a change could cause posting, publishing, identity disclosure, or unsafe automation.
17+
18+
## When to use
19+
- Reviewing write preflight behavior
20+
- Auditing public-facing text gates
21+
- Checking identity, consent, or safety logic before publication
22+
23+
## When not to use
24+
- Read-only scoring or classification changes
25+
- Deploy topology work without write behavior
26+
27+
## Required inputs
28+
- `src/policy/postingPolicy.ts`
29+
- `src/engagement/writePreflight.ts`
30+
- `src/boundary/publicGuard.ts`
31+
- `src/boundary/publicTextGuard.ts`
32+
33+
## Workflow
34+
1. Identify every branch that can result in a write or disclosure.
35+
2. Check the approval and consent gates in order.
36+
3. Verify public text and identity guards are fail-closed.
37+
4. Report any branch that relies on assumed operator intent.
38+
39+
## Expected outputs
40+
- SUMMARY
41+
- FINDINGS
42+
- RISKS
43+
- BOUNDARIES
44+
- NEXT ACTIONS
45+
46+
## Quality checks
47+
- Unsafe writes are blocked by default
48+
- Public text is validated before release
49+
- Identity disclosure behavior is deterministic
50+
51+
## Repo grounding notes
52+
- `src/policy/postingPolicy.ts`
53+
- `src/engagement/writePreflight.ts`
54+
- `src/boundary/publicGuard.ts`
55+
- `src/boundary/publicTextGuard.ts`
56+
- `src/router/permissions.ts`
57+
- `src/router/policyChecks.ts`
58+
- `src/identity/truthResolver.ts`
59+

‎skills/repo-specific/organoid-symbionts/skills/health-and-metrics-review/SKILL.md‎

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
name: health-and-metrics-review
3+
description: Reviews organoid_Symbionts health endpoints, glyph surfaces, and metrics payloads.
4+
version: 1.0.0
5+
repo: organoid_Symbionts
6+
classification: repo-specific
7+
safe_to_auto_run: true
8+
requires_repo_inputs: false
9+
produces_structured_output: true
10+
---
11+
12+
## Purpose
13+
Check the health and observability surfaces that operators use to decide whether the runtime is safe to keep running.
14+
15+
## Trigger
16+
Use when health endpoints, metrics, glyph status, or readiness logic changes.
17+
18+
## When to use
19+
- Reviewing `/health`, `/ready`, `/metrics`, or glyph output
20+
- Verifying readiness against the current state store
21+
- Auditing signal quality for alerts or dashboards
22+
23+
## When not to use
24+
- Pure business logic changes with no observability effect
25+
- Prompt edits that do not alter the HTTP surface
26+
27+
## Required inputs
28+
- `src/server.ts`
29+
- `src/observability/health.ts`
30+
- `src/observability/metrics.ts`
31+
- `src/observability/glyphStatus.ts`
32+
33+
## Workflow
34+
1. Enumerate the exposed health and metrics endpoints.
35+
2. Check the readiness criteria against the live state dependencies.
36+
3. Verify metric and glyph names are stable and explainable.
37+
4. Call out any degraded behavior that is intentional versus accidental.
38+
39+
## Expected outputs
40+
- SUMMARY
41+
- FINDINGS
42+
- RISKS
43+
- BOUNDARIES
44+
- NEXT ACTIONS
45+
46+
## Quality checks
47+
- Health endpoint is import-safe and side-effect controlled
48+
- Readiness checks the actual store, not a stub assumption
49+
- Metrics and glyph payloads are stable enough for operators
50+
51+
## Repo grounding notes
52+
- `src/server.ts`
53+
- `src/observability/health.ts`
54+
- `src/observability/metrics.ts`
55+
- `src/observability/glyphStatus.ts`
56+
- `src/observability/pulseHeart.ts`
57+
- `docs/operations/monitoring.md`
58+

‎skills/repo-specific/organoid-symbionts/skills/prompt-canon-and-embodiment-review/SKILL.md‎

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
name: prompt-canon-and-embodiment-review
3+
description: Reviews canonical prompt assets, embodiment fragments, and lore-facing guidance for organoid_Symbionts.
4+
version: 1.0.0
5+
repo: organoid_Symbionts
6+
classification: repo-specific
7+
safe_to_auto_run: true
8+
requires_repo_inputs: false
9+
produces_structured_output: true
10+
---
11+
12+
## Purpose
13+
Keep the canonical prompt and embodiment surface aligned with the repo's operational canon instead of letting parallel language drift in.
14+
15+
## Trigger
16+
Use when prompt fragments, embodiment definitions, or lore docs change.
17+
18+
## When to use
19+
- Reviewing prompt assembly or fragment loading
20+
- Checking embodiment labels, glyph anchors, or shared canon text
21+
- Auditing where runtime language is canonical versus legacy-compatible
22+
23+
## When not to use
24+
- Pure HTTP or state-store changes
25+
- Generic documentation cleanup unrelated to prompts
26+
27+
## Required inputs
28+
- `prompts/`
29+
- `src/context/prompts/organoid/`
30+
- `src/prompts/promptFragments.ts`
31+
- `docs/lore/`
32+
33+
## Workflow
34+
1. Identify the canonical prompt path used by the runtime.
35+
2. Check that embodiment fragments and legacy fragments are not mixed accidentally.
36+
3. Review lore text for operational clarity and canonical terminology.
37+
4. Note any fragment or prompt behavior that is inferred from loader code.
38+
39+
## Expected outputs
40+
- SUMMARY
41+
- FINDINGS
42+
- RISKS
43+
- BOUNDARIES
44+
- NEXT ACTIONS
45+
46+
## Quality checks
47+
- Canonical fragments are loaded from the expected prompt root
48+
- Legacy compatibility fragments stay isolated
49+
- Embodiment language matches the runtime contract
50+
51+
## Repo grounding notes
52+
- `prompts/fragments/sharedOrganoidCanon.md`
53+
- `prompts/fragments/sharedCanon.md`
54+
- `prompts/fragments/embodiments/*`
55+
- `prompts/presets/initiate-symbiosis.md`
56+
- `src/context/prompts/organoid/organoid_system.md`
57+
- `src/prompts/promptFragments.ts`
58+
- `docs/lore/ORGANOID_ORCHESTRATION.md`
59+

‎skills/repo-specific/organoid-symbionts/skills/render-blueprint-review/SKILL.md‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
name: render-blueprint-review
3+
description: Reviews the Render deployment blueprint, service graph, and command split for organoid_Symbionts.
4+
version: 1.0.0
5+
repo: organoid_Symbionts
6+
classification: repo-specific
7+
safe_to_auto_run: true
8+
requires_repo_inputs: false
9+
produces_structured_output: true
10+
---
11+
12+
## Purpose
13+
Review the Render blueprint as the primary production topology for the repo. This skill checks whether the worker, health service, landing app, and cron job are wired in a way that matches the runtime architecture.
14+
15+
## Trigger
16+
Use when a change touches deploy config, service startup commands, or the worker/landing split.
17+
18+
## When to use
19+
- Reviewing `render.yaml`
20+
- Checking whether `pnpm build`, `node dist/index.js`, or landing commands still match the deployed topology
21+
- Comparing service declarations against actual repo entrypoints
22+
23+
## When not to use
24+
- Pure code logic changes that do not affect deploy or service topology
25+
- Generic lint or formatting work
26+
27+
## Required inputs
28+
- `render.yaml`
29+
- `package.json`
30+
- `apps/landing/package.json`
31+
- `src/index.ts`
32+
- `src/server.ts`
33+
- `scripts/deploy-check.ts`
34+
- `scripts/symbiont-health-check.ts`
35+
36+
## Workflow
37+
1. Read `render.yaml` and the relevant package scripts.
38+
2. Map each service to a concrete entrypoint and build command.
39+
3. Check for topology drift, unsupported assumptions, or missing service separation.
40+
4. Flag any deploy-time behavior that is only implied rather than explicitly declared.
41+
42+
## Expected outputs
43+
- SUMMARY
44+
- FINDINGS
45+
- RISKS
46+
- BOUNDARIES
47+
- NEXT ACTIONS
48+
49+
## Quality checks
50+
- Worker start command resolves to a built entrypoint
51+
- Health service exposes the documented HTTP surface
52+
- Landing app is isolated from the worker runtime
53+
- Cron command points at a real script path
54+
55+
## Repo grounding notes
56+
- `render.yaml`
57+
- `package.json`
58+
- `apps/landing/package.json`
59+
- `src/index.ts`
60+
- `src/server.ts`
61+
- `scripts/deploy-check.ts`
62+
- `scripts/symbiont-health-check.ts`
63+

0 commit comments

Comments
 (0)