feat: improve jtbd-generator skill score (77% → 93%)#83
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @machaval 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `jtbd-generator`. Here's the before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | jtbd-generator | 77% | 93% | +16% | <details> <summary>Changes made</summary> **Description improvements:** - Expanded frontmatter description with additional concrete actions (`validate`, `update`) beyond just `generate` - Added capability details: "discovers matching API operations", "maps cross-step data flow", "produces validated hybrid-format files" - Converted description from block scalar (`|`) to quoted string format for better portability **Content improvements (biggest impact):** - Removed redundant intro paragraph and "How to Use" preamble that duplicated the frontmatter description - Extracted verbose Example Interaction, Error Handling, Tips for Quality Output, and Success Criteria sections — these explained concepts Claude already understands and bloated the file from 510 to 273 lines - Consolidated the 5 data flow detection rules into a compact "Data Flow Rules" section inline with the workflow - Replaced the 40-line Python utility API reference with a concise "References" section pointing to `lib/` module docstrings and the existing `README.md` - Line count dropped from 510 → 273, clearing the validation warning about file length **Unchanged skills:** - All other 27 skills left untouched </details> I also stress-tested your `jtbd-generator` skill against a few real-world task evals — the 6-step Parse → Discover → Analyze → Generate → Validate → Save workflow held up really well on multi-operation API deployments with cross-step data flow mapping. 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 @machaval, just a gentle nudge in case this got buried, let me know if you need any changes! |
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 @machaval 👋
great work. 28 skills covering the full Anypoint Platform lifecycle, from API discovery and portal curation to MCP server security and agent scanning. The split between platform operations skills and Mule development skills shows a clear understanding of the two audiences using this repo. Really thorough work.
ran your skills through
tessl skill reviewat work and found some targeted improvements forjtbd-generator. Here's the before/after:Changes made
Description improvements:
validate,update) beyond justgenerate|) to quoted string format for better portabilityContent improvements (biggest impact):
lib/module docstrings and the existingREADME.mdalso stress-tested your
jtbd-generatorskill against a few real-world task evals - the 6-step Parse → Discover → Analyze → Generate → Validate → Save workflow held up really well on multi-operation API deployments with cross-step data flow mapping. 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.