Eval
Multi-agent orchestration system with 21 specialized agents, automated workflows, and cost-optimized model routing.
npx -y skills add iabhisekbosepm/claude-god-setup --skill evalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate a complete Langfuse evaluation pipeline: auto-detect app type, create datasets, LLM-as-judge evaluators, scoring configs, and CI integration.
SKILL.md
1.6 KB, as published. Nobody here has run it
/eval — Langfuse Evaluation Pipeline Generator
Generate evaluation setup for: $ARGUMENTS
- Discover —
agents/eval-architect.mdStep 1: Explore codebase, detect LLM app type (RAG, chatbot, agent, code-gen, summarization, classification, extraction), identify prompts, traces, and data flows - Design —
agents/eval-architect.mdSteps 2-3: Select 4-8 eval dimensions from the dimension matrix, generate seed dataset with 10-20 items covering happy path, edge cases, and adversarial inputs - Generate —
agents/eval-architect.mdSteps 4-5: Write completeevals/directory: config.yaml, evaluators (LLM judge + heuristic), runner.py, ci_eval.py, .env.example - Setup —
agents/eval-architect.mdStep 6: IfLANGFUSE_SECRET_KEYis set, run setup_langfuse.py to create dataset and score configs in Langfuse. If not, skip gracefully with instructions. - Document —
agents/eval-architect.mdStep 7: Generate PM/SME-friendly README with quick start, architecture, and troubleshooting - Verify — Run verification checklist: correct app type? dimensions appropriate? dataset validates against schema? scripts importable? README clear?
Rules: Always include at least one heuristic evaluator. Never hardcode API keys. README must be understandable by non-developers.