feat: improve sla-calculation skill score (71% → 100%)#20
Open
yogesh-tessl wants to merge 2 commits into
Open
Conversation
The solution folder doesn't exist — only starter is present. Updated install path, PROJECT_ROOT example, and file tree accordingly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Hey 👋 @aksharguptaudacity 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 | |-------|--------|-------|--------| | sla-calculation | 71% | 100% | +29% | | ticket-classification | 77% | 77% | — | | company-analysis | 63% | 63% | — | *(Other skills scored 17–18% due to missing `name` frontmatter fields — not touched in this PR.)* <details> <summary>Changes made to <code>sla-calculation</code></summary> - **Cut 70% of content** (278 → 83 lines) by removing sections that duplicate the frontmatter (`When to Use This Skill`), repeat earlier content (`Tips`), or state things Claude already knows (`Success Criteria`, `Integration with Classification`) - **Added executable business-hours algorithm** — a concrete loop that walks through business days, replacing scattered pseudocode arithmetic - **Added validation checkpoint** (step 4) to confirm deadlines land on valid business hours and time remaining is non-negative - **Structured escalation triggers** as a scannable list with explicit thresholds - **Leveraged the existing `examples.md` bundle** for progressive disclosure — moved detailed worked scenarios out of the main file and into the reference, keeping the core skill concise - **Quoted the frontmatter description** to standard YAML format </details> I also stress-tested your `sla-calculation` skill against a few real-world task evals and it held up really well on business-hours calculations that span holidays and weekend carryover. 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 🙏
Author
|
hey @aksharguptaudacity 👋, just a friendly follow-up in case this got buried, happy to help move it forward! |
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 👋 @aksharguptaudacity
a full Claude Code course with 9 skills spanning ticket classification, code review, and even communication style is a really thoughtful curriculum. Love that you included both starter and solution versions so students can see the progression.
ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the before/after:Changes made to
sla-calculationWhen to Use This Skill), repeat earlier content (Tips), or state things Claude already knows (Success Criteria,Integration with Classification)examples.mdbundle for progressive disclosure - moved detailed worked scenarios out of the main file and into the reference, keeping the core skill concisealso stress-tested your
sla-calculationskill against a few real-world task evals and it held up really well on business-hours calculations that span holidays and weekend carryover. 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.