skill-check

Hey @thedaviddias 👋 I ran your skills through at work and found some targeted improvements. Here's the full before/after: This PR covers 5 of your 8 skills to keep the contribution focused and reviewable — the remaining 3 (agent-browser at 90%, github-gh at 95%, template-skill placeholder) are already in great shape or intentionally blank. Changes summary split-into-references: Added missing YAML frontmatter with name, description, and explicit trigger terms. The skill previously failed validation entirely (no frontmatter = 0% on all judge dimensions). tdd-methodoly-expert: Removed ~220 lines of verbose TDD textbook content that Claude already knows (Red-Green-Refactor explanations, phase principles, example flows). Consolidated into a tight workflow with explicit validation checkpoints at each phase. Kept the bundled tools section (most valuable part) and added well-signaled references to existing reference files. brainstorming: Removed the dot graph (won't render in Claude's context), eliminated the triple-redundancy (checklist + process flow diagram + "The Process" section all described the same workflow). Consolidated into a single clear 7-step workflow. Expanded description with specific actions and natural trigger terms. mcp-builder: Cut ~245 lines of generic software engineering advice (DRY, async/await, error handling concepts Claude already knows). Consolidated reference file listings from 5 separate locations into a single "Load Documentation" section. Kept agent-centric design principles (MCP-specific value) and the critical warning about long-running server processes. skill-check: Removed the "Testing this skill" section (meta-validation that doesn't help Claude perform the core task). Trimmed commands reference to essential commands. Added specific concrete actions to description (frontmatter schema, required fields, formatting issues, quality scoring with line numbers). Want your remaining skills optimised too? 🚀 This PR covers 5 of your 8 skills to keep the contribution focused and reviewable. We have tooling that can go further: Optimize remaining 3 skills automatically (same AI-powered pass as above) Add a GitHub Action — tesslio/skill-review-and-optimize — that automatically reviews (and optionally optimizes) any changed in future PRs. Review mode works with zero secrets; maintainers can add for AI suggestions and the comment flow. Interested? Just tick the box below and we'll raise a follow-up PR: [ ] Yes please! Raise a follow-up PR: optimize the remaining 3 skills + add the Tessl skill-review-and-optimize GitHub Action [ ] No thanks** — happy with the 5 skills in this PR Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute. Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide and ask it to optimize your skill. Ping me - @rohan-tessl - if you hit any snags. Thanks in advance 🙏