Skip to content

Add conversation_starter field to all 19 skills#71

Merged
timctfl merged 1 commit intomainfrom
add-conversation-starters
Apr 7, 2026
Merged

Add conversation_starter field to all 19 skills#71
timctfl merged 1 commit intomainfrom
add-conversation-starters

Conversation

@timctfl
Copy link
Copy Markdown
Owner

@timctfl timctfl commented Apr 7, 2026

Summary

  • Add conversation_starter field to all 19 skillshelf.yaml files
  • Update Python validator to accept optional string field
  • Update skillshelf-yaml-reference.md (both write-skill and adapt-skill copies) with field docs and example
  • Update CONTRIBUTING.md recommended fields table and YAML example
  • Update skill-authoring-guide.md with guidance to include the field

Context

The SkillShelf site has a "Here's how the conversation starts" section on every skill page, but it was hardcoded with a single placeholder. This adds the real opening message for each skill so the site can render them dynamically.

Test plan

  • python scripts/validate_skillshelf_metadata.py skills/*/ passes
  • Each skill's conversation_starter matches its Turn 1 content
  • No em dashes or real brand names in any starter

🤖 Generated with Claude Code

Add a conversation_starter field to every skillshelf.yaml. This is the
opening message the AI sends when a user starts the skill, displayed on
the skill page under "Here's how the conversation starts." Five skills
had existing blockquote openers in their SKILL.md; the other fourteen
were written from each skill's Turn 1 content.

Also updates:
- Python validator to accept optional conversation_starter string
- skillshelf-yaml-reference.md (both write-skill and adapt-skill copies)
- CONTRIBUTING.md recommended fields table and example
- skill-authoring-guide.md with a note to include the field

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@timctfl timctfl merged commit b9d20c9 into main Apr 7, 2026
1 check passed
@timctfl timctfl deleted the add-conversation-starters branch April 8, 2026 01:58
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.

2 participants