feat: improve sentry skill score from 84% to 94%#1
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @bleikamp 👋 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 | |-------|--------|-------|--------| | sentry | 84% | 94% | +10% | | kit-cli-navigator | 90% | 90% | — | | piglet | 86% | 86% | — | <details> <summary>Changes to <code>sentry</code></summary> - **Expanded frontmatter description** — added specific actions (stack traces, breadcrumbs, event details) and natural trigger terms (Sentry issue, exception, crash, error event, error tracking alerts) so Claude selects the skill more reliably. Fixed typo ("investgate" → "investigate"). - **Condensed fix guidance** — merged the Anti-Patterns, Defense in Depth, and Match Existing Codebase Patterns sections into a single concise "Fix Guidelines" section. Claude already understands these software engineering principles — a brief reminder is more token-efficient than three separate sections restating them. </details> I also stress-tested your `sentry` skill against a few real-world task evals and it held up really well on tracing null dereference root causes upstream through multi-layer call chains. 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 🙏
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 @bleikamp 👋
ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the before/after:Changes to
sentryalso stress-tested your
kit-cli-navigatorskill against a few real-world task evals and it held up really well on tracing null dereference root causes upstream through multi-layer call chains. Kudos for that.quick 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.