feat: improve external-component-migration skill score#4484
Open
yogesh-tessl wants to merge 1 commit into
Open
feat: improve external-component-migration skill score#4484yogesh-tessl wants to merge 1 commit into
yogesh-tessl wants to merge 1 commit into
Conversation
Hey @Skyscanner 👋 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 | |-------|--------|-------|--------| | backpack-external-component-migration | 83% | 90% | +7% | | backpack-v42-migration | 89% | 89% | — | | backpack-code-review-checklist | 88% | 88% | — | I focused on `backpack-external-component-migration` since it had the most improvement headroom — specifically in content conciseness and progressive disclosure. <details> <summary>Changes made</summary> **Content conciseness (1/3 → 2/3):** - Eliminated duplicate troubleshooting content — Phase 3.4 "Common Acceptance Failures" and "Common Issues & Solutions" covered the same problems (import paths, snapshot mismatches, Sass tokens). Merged and deduplicated into a single `TROUBLESHOOTING.md` bundle file - Removed "Why no HTML element spread?" rationale paragraph — the ❌ NO constraint rules already capture the requirement; the explanation restated what Claude already understands about React prop spreading - Removed duplicate "API Encapsulation for New Components" Notes section — identical to the ❌ NO rules in section 2.2 - Removed "Performance Considerations" Notes section — generic guidance Claude already knows (bundle size, dynamic imports, polyfills) - Moved changelog (~34 lines) from frontmatter to separate `CHANGELOG.md` **Progressive disclosure (2/3 → improved):** - Created `TROUBLESHOOTING.md` bundle file with merged, deduplicated troubleshooting content (lint errors, Sass tokens, module resolution, CSS classes, accessibility, coverage, snapshots) - Created `CHANGELOG.md` bundle file for version history - Added references to both bundle files in the References section **Frontmatter cleanup:** - Fixed `description` format from block scalar (|) to standard quoted string - Removed non-standard frontmatter keys (author, version, date, changelog) that triggered the frontmatter_unknown_keys warning — version history now lives in CHANGELOG.md - Validation warnings reduced from 2 to 1 **Net result:** SKILL.md reduced from 745 → 576 lines (−23%) while preserving all actionable content — code templates, workflow phases, verification checklist, and domain-specific guidance remain intact. </details> I also stress-tested your `backpack-external-component-migration` skill against a few real-world task evals and it held up really well on migrating an `unstable_backpack`-prefixed component with full Sass token conversion and accessibility test wiring. 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 🙏
Contributor
There was a problem hiding this comment.
Pull request overview
This PR refactors the backpack-external-component-migration Claude skill content to be more concise and to push detailed material into dedicated bundle files, improving readability while keeping key guidance discoverable.
Changes:
- Deduplicated and moved troubleshooting content into a new
TROUBLESHOOTING.md. - Moved version history out of frontmatter into a new
CHANGELOG.mdand linked it from the skill. - Simplified
SKILL.mdby removing repeated rationale/notes sections and cleaning up frontmatter keys/format.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .claude/skills/backpack-external-component-migration/TROUBLESHOOTING.md | New bundled troubleshooting guide consolidating common failure modes and fixes. |
| .claude/skills/backpack-external-component-migration/SKILL.md | Frontmatter cleanup + progressive-disclosure links; removed duplicated sections. |
| .claude/skills/backpack-external-component-migration/CHANGELOG.md | New bundled changelog containing prior version history previously in frontmatter. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| **Symptom:** Lint fails with errors in `dist-sassdoc/`, `dist/`, or other generated directories | ||
|
|
||
| **Fix:** Ensure `.eslintignore` includes all generated directories: |
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
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 Skyscanner (@Skyscanner) 👋
truly impressive. 538 stars on a design system that bridges Figma and code, with workflows for syncing variables and code connect, that's a serious investment in keeping design and engineering in sync. The migration skills for v42 and external components are a nice touch for helping teams upgrade smoothly.
ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the before/after:I focused on
backpack-external-component-migrationsince it had the most improvement headroom, specifically in content conciseness and progressive disclosure.Changes made
Content conciseness (1/3 → 2/3):
TROUBLESHOOTING.mdbundle fileCHANGELOG.mdProgressive disclosure (2/3 → improved):
TROUBLESHOOTING.mdbundle file with merged, deduplicated troubleshooting content (lint errors, Sass tokens, module resolution, CSS classes, accessibility, coverage, snapshots)CHANGELOG.mdbundle file for version historyFrontmatter cleanup:
descriptionformat from block scalar (|) to standard quoted stringquick 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.