Skip to content

Fix SKILL.md scaffold and wiring-only unit test#11

Open
JoeCardoso13 wants to merge 1 commit intomainfrom
fix/skill-md-scaffold-unit-test
Open

Fix SKILL.md scaffold and wiring-only unit test#11
JoeCardoso13 wants to merge 1 commit intomainfrom
fix/skill-md-scaffold-unit-test

Conversation

@JoeCardoso13
Copy link
Contributor

Summary

  • Replace the fully-populated SKILL.md (hardcoded list_items/get_item) with a TODO scaffold — frontmatter + section headings, no tool names
  • Change test_skill_resource_readable from asserting specific tool names to asserting non-empty content with expected structure (## Tools heading)

This fixes a break in the build-mcpb pipeline where Phase 3 (Implement & Verify) replaces template tools with real ones, but SKILL.md isn't customized until Phase 5 (Embed Skill). The unit test was asserting tool names that no longer existed.

Related: NimbleBrainInc/contributor-toolkit#43

Test plan

  • uv run pytest tests/ -v — all 25 tests pass with the scaffold SKILL.md

The template shipped a fully-populated SKILL.md with hardcoded
list_items/get_item tool names, and test_skill_resource_readable
asserted those names. This broke the build-mcpb pipeline at Phase 3
when tools were replaced with real ones but SKILL.md wasn't updated
until Phase 5.

SKILL.md is now a structural scaffold (frontmatter + section headings,
no tool names). The unit test asserts the resource is non-empty and
has the expected structure, without assuming any specific tool names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant