openskills-e2e-test-runbook
Run deterministic OpenSkills end-to-end validation across runtime tests and example agents, then report tool calls, activation behavior, and regressions.
git clone --depth 1 https://github.com/Geeksfino/openskills /tmp/openskills-e2e-test-runbook && cp -r /tmp/openskills-e2e-test-runbook/.cursor/skills/openskills-e2e-test-runbook ~/.claude/skills/openskills-e2e-test-runbookSKILL.md
# OpenSkills E2E Test Runbook Use this skill for confidence checks before merging runtime, tooling, or example-agent changes. ## Test Layers 1. Runtime regression tests 2. Sandbox-focused tests 3. Example-agent behavior checks 4. Optional binding smoke tests ## Baseline Commands ```bash cargo test -p openskills-runtime ``` Example-agent checks (from example directories): ```bash npm install npm start "What skills are available?" npm start "Create a new skill called 'note-taker'." ``` ## E2E Expectations - Skills discover successfully. - Skill activation occurs for matching prompts. - Tool calls align with intent (activation, file reads/writes, script runs). - No unexpected sandbox failures. ## Reporting Format - What was run - What passed - What failed - Repro command for each failure - Suggested next fix
Maintain compatibility between openskills-runtime and language bindings (TypeScript, Python), including feature flags, build configuration, and smoke verification.
Route OpenSkills development tasks to the right project skill or subagent, including sequencing rules for debugging, feature work, regression checks, and release readiness.
Enforce clean separation between core openskills-runtime and optional WASM build plugins so plugin compilation does not break runtime consumers or language bindings.
Prepare and validate OpenSkills release readiness across runtime, bindings, examples, and regression gates with a deterministic checklist and go/no-go outcome.
Diagnose openskills-runtime execution failures in sandboxed paths (Landlock, seatbelt, native script execution, wasm execution) and produce root-cause-first findings with minimal-risk remediation steps.
Create and refine OpenSkills-compatible skills (SKILL.md + optional resources) with strong metadata, clear activation triggers, and reliable execution guidance.
Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
Explains code clearly and thoroughly. Use when asked to explain, clarify, or teach about code snippets, functions, or concepts.