You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: skills/extropy/SKILL.md
+38Lines changed: 38 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,36 @@ name: extropy
3
3
description: "Execution-first operator for Extropy: run pipelines, diagnose failures, and deliver evidence-backed simulation analysis using current CLI contracts."
- provider API keys via environment variables only
33
+
notes:
34
+
- extropy reads model/provider settings from ~/.config/extropy/config.json
35
+
- extropy may load .env from the current working directory
6
36
---
7
37
8
38
# Extropy Operator
@@ -17,6 +47,14 @@ Run experiments end to end, with strict quality gates and reproducible commands.
17
47
4. Keep assumptions visible and minimal.
18
48
5. Escalate after repeated failure of the same gate.
19
49
50
+
## Runtime Dependencies and Credential Scope
51
+
52
+
- Required binary: `extropy` must be installed and on `PATH`.
53
+
- Config files read: `~/.config/extropy/config.json` and project/local `.env` (if present).
54
+
- Credentials expected: provider API keys from env vars (`OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, `OPENROUTER_API_KEY`, `DEEPSEEK_API_KEY`, `AZURE_API_KEY`/`AZURE_OPENAI_API_KEY`).
55
+
- Azure endpoint vars: `AZURE_ENDPOINT` or `AZURE_OPENAI_ENDPOINT` when using Azure providers.
56
+
- Safety boundary: only access credentials/config needed to execute extropy commands for the requested study/scenario, and avoid reading unrelated files.
0 commit comments