SKILLEMALL.ai
GitHub ↗ RU Sign in

CB openexec-api

Interact with the Open Executive FastAPI backend via curl. Use this skill when the user asks to hit /chat, /today, /people, /scheduled_actions, /architecture/*, /health/*, /fixtures/*, /audit/*, or any HTTP endpoint on the Open Executive API, local or deployed. Authenticates via $BACKEND_SHARED_SECRET in the x-api-key header. Tiered safety: GET runs freely, mutating POSTs need explicit confirmation.

SenteLabsAI/OpenExecutive Agent Skills author: SenteLabsAI Apache-2.0 1 file body ≈ 1 832 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Interact with the Open Executive FastAPI backend via curl.

As a process B 72/100 · Nearly there — weak spots: inputs and preconditions

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
75
Run on models
none yet
Process rating
B
72/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
55
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 5

    ✓ No critical or high findings

    Medium and low: 5
    • low Exfiltration net-credential-use SKILL.md:3
      Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
      description: Interact with the Open Executive FastAPI backend via curl. Use this skill when the user asks to hit /chat, /today, /people, /scheduled_actions, /architecture/*, /health/*, /fixtures/*, /a
      security skill
    • low Exfiltration net-credential-use SKILL.md:49
      Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
      curl -s -H "x-api-key: $BACKEND_SHARED_SECRET" $OE_API/health | jq
      security skill
    • low Exfiltration net-credential-use SKILL.md:50
      Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
      curl -s -H "x-api-key: $BACKEND_SHARED_SECRET" $OE_API/health/honcho | jq
      security skill
    • low Exfiltration net-credential-use SKILL.md:63
      Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
      curl -s -H "x-api-key: $BACKEND_SHARED_SECRET" $OE_API/architecture/sections | jq '.sections[] | {id, fresh, generated_at}'
      security skill
    • low Exfiltration net-credential-use SKILL.md:66
      Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
      curl -s -H "x-api-key: $BACKEND_SHARED_SECRET" $OE_API/architecture/sections/honcho | jq
      security skill

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Interact with the Open Executive FastAPI backend via curl. Use thi… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value

    Process rating: all ten parameters 72/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 100Steps. 17 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1832 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 14 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 402: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 17 items
    • +3Output format is stated explicitly
    • +4Has examples (10 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.