Claude-skill-registry-data looplia-e2e
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry-data
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry-data "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/looplia-e2e" ~/.claude/skills/majiayu000-claude-skill-registry-data-looplia-e2e && rm -rf "$T"
manifest:
data/looplia-e2e/SKILL.mdsource content
Looplia E2E Test Skill
End-to-end testing for looplia CLI from local source.
Quick Start
# Set API key in .env echo "ZENMUX_API_KEY=your-key" >> .env # Run E2E test .claude/skills/looplia-e2e/scripts/e2e.sh
What It Tests
The script performs these steps:
- Build - Compiles the CLI from source
- Reset - Removes
for fresh start~/.looplia - Init - Initializes workspace with plugins
- Configure - Sets provider to ZenMux MiniMax M2.1
- Build Command - Tests workflow generation (HN AI news aggregator)
- Run Command - Executes writing-kit workflow with ai-healthcare.md
- Verify - Checks outputs, validation state, and logs
Expected Outputs
Build command:
~/.looplia/workflows/e2e-build-test.md # Generated workflow file ~/.looplia/sandbox/build-<id>/ ├── validation.json # workflowValidated: true └── logs/ └── *.log # Execution logs
Run command:
~/.looplia/sandbox/<run-id>/ ├── outputs/ │ ├── summary.json # Stage 1: Content analysis │ ├── ideas.json # Stage 2: Idea generation │ └── writing-kit.json # Stage 3: Final output ├── validation.json # All steps validated: true └── logs/ └── *.log # Execution logs
Success Criteria
Build command:
- Workflow file created at
~/.looplia/workflows/e2e-build-test.md - validation.json shows
workflowValidated: true
Run command:
- 3 output files created (summary.json, ideas.json, writing-kit.json)
- All 3 steps validated in validation.json
- Final output writing-kit.json exists
Troubleshooting
Transient API errors (retry usually works): The ZenMux provider may occasionally return transient errors like "duplicate tool_call id". This is a provider-side issue, not a workflow bug. Simply run the test again:
# Just retry - second run usually succeeds .claude/skills/looplia-e2e/scripts/e2e.sh
API key issues:
# Verify .env exists and contains ZENMUX_API_KEY cat .env | grep ZENMUX_API_KEY
Workspace issues:
# Manual reset rm -rf ~/.looplia && looplia init --yes
Build issues:
# Clean rebuild rm -rf apps/cli/dist && bun run build
File Structure
.claude/skills/looplia-e2e/ ├── SKILL.md # This file ├── scripts/ │ └── e2e.sh # E2E test script └── assets/ └── ai-healthcare.md # Test content fixture