01 — TL;DR
If you need output specificity above all else, pick internal-comms (4.6/5). experimental-design (4.3/5) is a reasonable alternative if you're already in its source ecosystem. They overlap in agent skill territory.
Side by side
4.3/5
4.6/5
Where they differ
- Trigger clarity. trigger clarity: experimental-design and internal-comms score essentially the same (5.0 vs 5.0). Neither has an edge here.
- Output specificity. output specificity: a meaningful gap. internal-comms scores 3.5 vs 4.5 for the other. If you need this dimension, internal-comms is the right pick.
- Scope precision. scope precision: experimental-design and internal-comms score essentially the same (4.5 vs 4.5). Neither has an edge here.
- Self-containment. self-containment: internal-comms is clearly stronger (4.0 vs 4.5). For workloads where this dimension matters, prefer internal-comms.
- Reusability. reusability: experimental-design and internal-comms score essentially the same (4.0 vs 4.0). Neither has an edge here.
Which to pick
When to choose experimental-design
- You weight community adoption — experimental-design's upstream repo has 28,193 stars vs 15,974.
- The agent skill convention you're working in matches experimental-design's scope.
When to choose internal-comms
- Your workload emphasizes output specificity — internal-comms scores 3.5 vs 4.5 here.
- Your workload emphasizes self-containment — internal-comms scores 4.0 vs 4.5 here.
- Multi-source consensus matters to you — internal-comms appears in 3 of our tracked sources (experimental-design: 1).
Scenario by scenario
| Scenario | Winner | Why |
|---|---|---|
| Agent must auto-select between many agent skills | either | Trigger clarity decides — clearer triggers reduce routing errors. |
| Output must be a specific file format or structured data | internal-comms | Output specificity determines whether downstream tools can rely on the result. |
| Skill must be readable and complete out of the box | internal-comms | Self-containment matters when you're not the original author. |
| Cross-team or cross-project reuse expected | either | Reusability separates one-off scripts from durable building blocks. |
Common questions
- Which is better, experimental-design or internal-comms?
- internal-comms ranks higher overall (4.6 vs 4.3 on our 0–5 rubric). That said, the better choice depends on which dimensions matter most for your use case.
- Are experimental-design and internal-comms both free to use?
- Both skills are free and open-source (or freely licensed). experimental-design: See source repo. internal-comms: See source repo. Installation has no cost; usage costs depend on the underlying LLM tokens consumed when you invoke the skill.
- Can I install both experimental-design and internal-comms at the same time?
- Yes. Agent skills are not exclusive — an agent runtime (Claude Code, Codex, etc.) can have many skills installed and route to whichever matches the current task. Installing both is a low-cost way to keep your options open.
- Where do these skills come from?
- experimental-design is sourced from skillsmp.com (curated marketplace). internal-comms is sourced from skillsmp.com (curated marketplace). We verify each skill across multiple sources where possible; experimental-design appears in 1 source, internal-comms in 3.