SkillAgentSearch skills...

skillshare-cli-e2e-test

Run isolated E2E tests in devcontainer from ai_docs/tests runbooks. Use this skill whenever the user asks to: run an E2E test, execute a test runbook, validate a feature end-to-end, create a new runbook, or test CLI behavior in isolation.

Install / Use

npx skills add runkids/skillshare --skill skillshare-cli-e2e-test

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

95/100

Category

Operations

Supported Platforms

Universal

Our assessment of skillshare-cli-e2e-test

skillshare-cli-e2e-test scores 95/100 on our quality scale, 115th of 745 Operations skills we index (top 16%).

Its SKILL.md is 18 KB long, well organised into 38 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

With 2,689 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so skillshare-cli-e2e-test is actively maintained.
  • Our last check on 2026-11-16 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

skillshare-cli-e2e-test compared with similar skills

All 4 of these similar skills score higher than skillshare-cli-e2e-test; compare them before choosing.

SkillScoreStarsUpdatedFormat
skillshare-cli-e2e-test (this skill)by runkids952.7k54d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install skillshare-cli-e2e-test?
Run npx skills add runkids/skillshare --skill skillshare-cli-e2e-test. The install tabs above show the steps for each supported agent.
Which AI agents does skillshare-cli-e2e-test work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is skillshare-cli-e2e-test safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is skillshare-cli-e2e-test still maintained?
The repository was last updated about 2 months ago, so skillshare-cli-e2e-test is actively maintained.

name: skillshare-cli-e2e-test description: >- Run isolated E2E tests in devcontainer from ai_docs/tests runbooks. Use this skill whenever the user asks to: run an E2E test, execute a test runbook, validate a feature end-to-end, create a new runbook, or test CLI behavior in isolation. If you need to run a multi-step CLI validation sequence (init → install → sync → verify), this is the skill — it handles ssenv isolation, flag verification, and structured reporting. Prefer this over ad-hoc docker exec sequences for any test that follows a runbook or needs reproducible isolation. argument-hint: "[runbook-name | new]" metadata: targets: [claude, universal]

Run isolated E2E tests in devcontainer. $ARGUMENTS specifies runbook name or "new".

Before acting, run python3 scripts/ai-context.py testing. The topic is the source of truth for isolation, runbook quality and reporting rules; this skill retains the execution flow and mdproof recipes.

Flow

Phase 0: Environment Check

  1. Confirm devcontainer is running and get container ID:

    CONTAINER=$(docker compose -f .devcontainer/docker-compose.yml ps -q skillshare-devcontainer)
    
    • If empty → prompt user: docker compose -f .devcontainer/docker-compose.yml up -d
    • Ensure CONTAINER is set for all subsequent docker exec calls.
  2. Confirm Linux binary is available:

    docker exec $CONTAINER bash -c \
      '/workspace/.devcontainer/ensure-skillshare-linux-binary.sh && ss version'
    
  3. Confirm mdproof is installed:

    docker exec $CONTAINER /workspace/.devcontainer/ensure-mdproof.sh
    

    This auto-installs from GitHub release, or falls back to /workspace/bin/mdproof (local dev binary).

  4. Check for lessons learned from previous runs:

    test -f /workspace/.mdproof/lessons-learned.md && cat /workspace/.mdproof/lessons-learned.md
    

    If the file exists, read it before writing or debugging runbooks — it contains known gotchas and assertion patterns.

Phase 1: Detect Scope

  1. Preview all available runbooks via the container:

    docker exec $CONTAINER mdproof --dry-run --report json /workspace/ai_docs/tests/
    

    This returns JSON with every runbook's steps, commands, and expected assertions — no manual markdown parsing needed. Use this to understand what each runbook covers.

  2. Identify recent changes (unstaged + recent commits):

    git diff --name-only HEAD~3
    
  3. Match changes to relevant runbooks (compare changed file paths against step commands in the JSON output).

Phase 2: Select Tests

Prompt user (via AskUserQuestion):

  • Option A: Run existing runbook (list all available + mark those related to recent changes)
  • Option B: Auto-generate new test script based on recent changes
  • Option C: If $ARGUMENTS specifies a runbook, skip to Phase 3

Phase 3: Prepare & Execute

Running existing runbook:

  1. Create isolated environment with auto-initialization:

    ENV_NAME="e2e-$(date +%Y%m%d-%H%M%S)"
    
    # Use --init to automatically run 'ss init -g' with all targets
    docker exec $CONTAINER ssenv create "$ENV_NAME" --init
    
  2. Execute the entire runbook via mdproof inside the container:

    docker exec $CONTAINER env SKILLSHARE_DEV_ALLOW_WORKSPACE_PROJECT=1 \
      ssenv enter "$ENV_NAME" -- \
      mdproof --report json \
      /workspace/ai_docs/tests/<runbook_file>.md
    

    mdproof executes each step (bash -c <command>) in the ssenv-isolated HOME, then returns structured JSON:

    {
      "version": "1",
      "runbook": "<runbook_file>.md",
      "duration_ms": 12345,
      "summary": { "total": 7, "passed": 5, "failed": 1, "skipped": 1 },
      "steps": [
        {
          "step": { "number": 1, "title": "...", "command": "...", "expected": ["..."] },
          "status": "passed",    // "passed" | "failed" | "skipped"
          "exit_code": 0,
          "stdout": "...",
          "stderr": "..."
        }
      ]
    }
    
  3. Analyze the JSON output:

    • All passed → proceed to Phase 4
    • Any failed → filter for failures only (full JSON can be too large for terminal output):
      mdproof --report json runbook.md 2>&1 | jq '{
        summary: .summary,
        failed: [.steps[] | select(.status == "failed") | {
          step: .step.number, title: .step.title,
          exit_code: .exit_code,
          failed_assertions: [.assertions[]? | select(.matched == false) | .pattern],
          stderr: (.stderr // "" | .[0:200])
        }]
      }'
      
    • Skipped steps (executor=manual) → these need manual verification, run them individually:
      docker exec $CONTAINER env SKILLSHARE_DEV_ALLOW_WORKSPACE_PROJECT=1 \
        ssenv enter "$ENV_NAME" -- <command from step.command>
      
  4. For failed steps, debug individually using manual docker exec (same as before):

    docker exec $CONTAINER env SKILLSHARE_DEV_ALLOW_WORKSPACE_PROJECT=1 \
      ssenv enter "$ENV_NAME" -- bash -c '<failed step command>'
    
    • Prefer --json + jq for assertions — see the JSON Reference below

Generating new runbook:

  1. Read git diff HEAD~3 to find changed files in cmd/skillshare/ or internal/
  2. Read changed files to understand new/modified functionality
  3. Validate all CLI flags before writing — for every ss <command> <flag> in the runbook:
    • Grep cmd/skillshare/<command>.go for the exact flag string (e.g. "--force")
    • Run ss <command> --help inside container if needed
    • Common mistakes to avoid:
      • uninstall --yes → wrong, use --force / -f
      • init --target <name> → wrong, init has no --target flag
      • init -p has a completely separate flag set from global init — only supports --targets, --discover, --select, --mode, --dry-run. Global-only flags like --no-copy, --no-skill, --no-git, --all-targets, --force do NOT exist in project mode
      • Audit custom rules: disable by rule ID (e.g. prompt-injection-0, prompt-injection-1), NOT pattern name (e.g. prompt-injection). Rule IDs are in internal/audit/rules.yaml
  4. Generate new runbook to ai_docs/tests/<slug>_runbook.md, following existing conventions:
    • YAML-free, pure Markdown
    • Has Scope, Environment, Steps (each with bash + Expected), Pass Criteria
    • Use jq: assertions in Expected blocks for JSON commands — e.g. - jq: .extras | length == 1. This is a native mdproof assertion type, NOT a bash jq pipe
    • Use --json + jq -e in bash for inline verification within multi-command steps
    • Config idempotency — never bare cat >> config.yaml; always prepend sed -i '/^section:/,$d' to remove existing section first, or use CLI commands (ss extras init, ss extras remove --force) that handle duplicates
    • Check ai_docs/tests/mdproof.json for project-level config (build, setup, teardown, step_setup, timeout) that affects all runbooks
    • Check .mdproof/lessons-learned.md for known assertion patterns and gotchas
  5. Run the runbook quality checklist (see below) before executing
  6. Then execute the new runbook (same flow as above)

Phase 4: Cleanup & Report

  1. Ask user before cleanup (via AskUserQuestion):

    • Option A: Delete ssenv environment now
    • Option B: Keep for manual debugging (print env name for later ssenv delete)
  2. If user chose Option A:

    docker exec $CONTAINER ssenv delete "$ENV_NAME" --force
    
  3. Output summary (derived from the runbook JSON output):

    ── E2E Test Report ──
    
    Runbook:  {runbook name}
    Env:      {ENV_NAME}
    Duration: {duration_ms}ms
    
    Step 1: {title}  PASS
    Step 2: {title}  PASS
    Step 3: {title}  FAIL ← exit_code={N}, stderr: {error detail}
    ...
    
    Result: {passed}/{total} passed ({skipped} skipped)
    

    All values come directly from mdproof's JSON output — summary.passed, summary.total, steps[].step.title, steps[].status.

  4. If any FAIL → distinguish between runbook bug vs real bug:

    • Runbook bug: wrong flag, wrong file path, stale assertion → fix runbook, re-run step
    • Real bug: CLI misbehavior → analyze cause, provide fix suggestions
  5. Retrospective — ask user (via AskUserQuestion):

    Did you encounter any friction during this test run that the skill or runbook could handle better?

    • Option A: Yes, improve e2e skill — review test friction (wrong flags, stale assertions, missing checklist items, unclear instructions), then update SKILL.md and/or runbooks
    • Option B: Yes, but only fix the runbook — fix the specific runbook without changing the skill itself
    • Option C: No, skip

    Improvement targets:

    • SKILL.md: add new checklist items, common-mistake examples, or rule clarifications learned from this run
    • Runbooks: fix stale assertions (e.g. config.yaml → registry.yaml), wrong flags, outdated paths
    • Both: when a systemic issue (e.g. a refactor changed file locations) affects both the skill's guidance and existing runbooks

Runbook Quality Checklist

Before executing a newly generated runbook, verify:

  • [ ] All CLI flags exist — every ss <cmd> --flag was grep-verified against source
  • [ ] --init interaction — if runbook has ss init, account for ssenv create --init already initializing (add --force to re-init, or skip init step)
  • [ ] --init creates default extras — ssenv create --init creates a rules extra by default. Runbooks that assume an empty extras list must add cleanup first: ss extras remove rules --force -g 2>/dev/null || true + rm -rf ~/.claude/rules
  • [ ] Correct confirmation flags — uninstall uses --force (not --yes); init re-run needs no flag (just fails gracefully)
  • [ ] Skill data in registry.yaml — assertions about installed skills check registry.yaml, NOT config.yaml; config.yaml should never contain skills:
  • [ ] File existence timing — registry.yaml is only created after first install/reconcile, not on ss init
  • [ ] Project mode paths — project commands use .skillshare/ not ~/.config/skillshare/
  • [ ] Project init flags — init -p only supports --targets, --discover, --select, --mode, --dry-run; global-only flags (--no-copy, --no-skill, --no-git, --all-targets, --force) are not available
  • [ ] Audit rule IDs — custom rules in audit-rules.yaml use rule IDs (e.g. prompt-injection-0), not pattern names (e.g. prompt-injection). Verify IDs against internal/audit/rules.yaml
  • [ ] Use --json for assertions — if the command supports --json, use it with jq instead of grepping human-readable output. Text output changes between versions; JSON structure is stable
  • [ ] Expected = actual substrings, NOT descriptions — the runbook assertion engine does case-insensitive substring matching. Write - Installed or - cangjie-docs-navigator, NOT - Install completes without error or - Output contains at least one skill. Negation: use Not <substring> prefix (e.g. - Not cangjie-docs-navigator)
  • [ ] Skill name ≠ repo name — after ss install <repo>, the actual skill name may differ from the repo name (e.g. repo cangjie-docs-mcp → skill cangjie-docs-navigator). Always verify the installed skill name via ss list before writing uninstall/check steps
  • [ ] /tmp/ cleanup — ssenv only isolates $HOME; /tmp/ is shared across runs. Any step using /tmp/<path> must start with rm -rf /tmp/<path> to avoid stale state from previous runs
  • [ ] echo > symlink writes through — echo "content" > path where path is a symlink writes to the symlink's target, it does NOT replace the symlink with a real file. To create a local (non-managed) file at a symlinked path: either use a different filename, or rm the symlink first then echo
  • [ ] Extras source path layout — e

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryOperations
Updated1mo ago
Forks167

Languages

Go

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions