feat: improve component-scaffold skill score 10% → 89%#474
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @art-alexeyenko 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `content-sdk-component-scaffold`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | content-sdk-component-scaffold | 10% | 89% | +79% | | content-sdk-component-registration | 89% | 89% | 0% | | content-sdk-field-usage-image-link-text | 83% | 83% | 0% | | content-sdk-route-configuration | 83% | 83% | 0% | | content-sdk-editing-safe-rendering | 70% | 70% | 0% | | content-sdk-troubleshoot-editing | 69% | 69% | 0% | The remaining 8 skills (`component-data-strategy`, `component-variants`, `dictionary-and-i18n`, `graphql-data-fetching`, `multisite-management`, `site-setup-and-env`, `sitemap-robots`, `upgrade-assistant`) also scored 10% due to the same unquoted-colon frontmatter issue — happy to send follow-up PRs for those if this one looks good. - [x] This PR follows the [Contribution Guide](https://github.com/Sitecore/content-sdk/blob/dev/CONTRIBUTING.md) - [ ] Changelog updated - [ ] Upgrade guide entry added ## Description / Motivation The `content-sdk-component-scaffold` skill scored 10% because its YAML frontmatter description contained an unquoted colon (`App Router: decide Server vs Client...`) which breaks YAML parsing — the review tool couldn't evaluate the skill at all. I picked this skill because it's the first one listed in Skills.md and the most common developer starting point (scaffolding new components). Changes applied to both the App Router and Pages Router template versions: <details> <summary>Changes made</summary> - **Fixed YAML frontmatter**: Wrapped the `description` field in quotes to fix the YAML parsing error caused by an unquoted colon - **Enhanced description**: Added specific file paths (`.sitecore/component-map.ts`, `.sitecore/component-map.client.ts`) and additional trigger terms (`React component`, `layout placeholders`) for better skill matching - **Added concrete code example**: Included a copy-paste-ready TSX snippet showing a properly structured component with typed props, `Field<string>` imports, and params handling - **Structured workflow as numbered steps**: Converted bullet points to a clear 1→2→3→4→5 sequence (create file → define props → decide server/client → register → build & verify) - **Added verification step**: Step 5 now includes confirming the component resolves in layout preview or editing mode after building </details> I also stress-tested your `content-sdk-component-registration` skill against a few real-world task evals and it held up really well on server-vs-client component map routing — scored 89% out of the box. 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. ## Testing Details - [x] Manual Test/Other — Ran `tessl skill review` before and after on both template versions. Both went from 10% → 89%. Description dimension: 100%. Content dimension: 73%. ## Types of changes - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) Thanks in advance 🙏
|
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
1 participant
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 @art-alexeyenko 👋
this is really well put together. Having
.agents/skills, Copilot instructions, Cursor config, and Windsurf rules all in one place makes the AI tooling setup feel comprehensive and intentional. TheSkills.mdas a top-level index, alongsideAGENTS.mdandCLAUDE.md, is a great touch too.ran your skills through
tessl skill reviewat work and found some targeted improvements forcontent-sdk-component-scaffold. Here's the full before/after:The remaining 8 skills (
component-data-strategy,component-variants,dictionary-and-i18n,graphql-data-fetching,multisite-management,site-setup-and-env,sitemap-robots,upgrade-assistant) also scored 10% due to the same unquoted-colon frontmatter issue. Happy to send follow-up PRs for those if this one looks good.Changes applied to both the App Router and Pages Router template versions:
Changes made
descriptionfield in quotes to fix the YAML parsing error caused by an unquoted colon.sitecore/component-map.ts,.sitecore/component-map.client.ts) and additional trigger terms (React component,layout placeholders) for better skill matchingField<string>imports, and params handlingquick 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.