feat: improve skill score for platform-changelog-formatter#1421
Open
yogesh-tessl wants to merge 1 commit into
Open
feat: improve skill score for platform-changelog-formatter#1421yogesh-tessl wants to merge 1 commit into
yogesh-tessl wants to merge 1 commit into
Conversation
Hey @llewellyn-sl 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | platform-changelog-formatter | 10% | 90% | +80% | | openapi-overlay-generator | 84% | — | — | | docs-state-assessment | 90% | — | — | | os-changelog-formatter | 90% | — | — | | feature-docs | 90% | — | — | | release-impact-assessment | 77% | — | — | | editorial-review | 71% | — | — | The `platform-changelog-formatter` skill had the most headroom — it was scoring 10% because it was missing YAML frontmatter entirely, which meant the skill evaluator couldn't parse the description or name fields. The content itself was already solid. <details> <summary>Changes summary</summary> **platform-changelog-formatter (10% → 90%, +80%)**: - Added proper YAML frontmatter with `name` and `description` fields (the critical fix — this alone unlocked the description score from 0% to 100%) - Crafted a description with specific trigger terms (`Platform changelog`, `changelog style`, `Cloud or Enterprise releases`, file paths), a "Use when" clause, and explicit disambiguation from `os-changelog-formatter` - Removed redundant sections: standalone "Description" heading (now in frontmatter), "Deployment" section (no value), duplicated scope declarations that appeared in description, step 2, and "Important notes" - Streamlined heading hierarchy from nested `###` subsections to flat `##` numbered steps - Condensed output section and "Important notes" into tighter form - Preserved all domain expertise: style rules, component categories with ordering, Cloud vs Enterprise specifics, before/after example, and quality checklist </details> I also stress-tested your `platform-changelog-formatter` skill against a few real-world task evals and it held up really well on component-based categorization of mixed Studios, Compute environments, and Pipeline entries with the Cloud vs Enterprise context switching. Kudos for that. 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](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me — [@yogesh-tessl](https://github.com/yogesh-tessl) — if you hit any snags. Thanks in advance 🙏
|
| Name | Link |
|---|---|
| 🔨 Latest commit | 424b966 |
Contributor
|
Hi, @yogesh-tessl! Thanks for this PR, it's super-useful. I'll table it for team review and get back to you ASAP. :) |
justinegeffen
added
do not merge
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey @llewellyn-sl 👋
ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the before/after:The
platform-changelog-formatterskill had the most headroom. It was scoring 10% because it was missing YAML frontmatter entirely, which meant the skill evaluator couldn't parse the description or name fields. The content itself was already solid.Changes summary
platform-changelog-formatter (10% → 90%, +80%):
nameanddescriptionfields (the critical fix - this alone unlocked the description score from 0% to 100%)Platform changelog,changelog style,Cloud or Enterprise releases, file paths), a "Use when" clause, and explicit disambiguation fromos-changelog-formatter###subsections to flat##numbered stepsquick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.
if you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.