build-assistant

I took a look at your build-assistant skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 74/100, solid C-grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Writing Style (9/10)—the docs are clear and readable. Weakest is Spec Compliance (10/15)—there are some naming convention issues and missing trigger phrases that are easy wins.

What's Working Well

• Clear documentation structure - Your SKILL.md does a good job layering information: overview → component types → specific workflows. That's PDA done right.
• Practical templates and examples - The skill ships with actual templates for agents, commands, skills, and plugins. That's genuinely useful and shows you thought through what people need.
• Validation scripts - The validate-*.sh scripts provide real feedback loops. People can run them, check output, fix things. That's excellent utility (18/20).
• Consistent terminology - "component", "manifest", "structure" - you use terms the same way throughout, which makes it easy to follow.

The Big One: Name Convention Issues

Your frontmatter has name: Build-Assistant but it should be lowercase: name: build-assistant. That's a spec compliance issue. Also, when I look at the directory structure, there's a mismatch between the skill name in metadata and where it lives. These seem small, but the spec is strict here because consistent naming makes skills discoverable and parseable by tooling.

Fix: Update line 1 of your SKILL.md frontmatter from Build-Assistant to build-assistant. Check that the directory path matches (should be build-assistant/, not Build-Assistant/). ...