feat: improve devvit-docs skill score (85% → 89%)#1
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @mwood23 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `devvit-docs`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | devvit-docs | 85% | 89% | +4% | | devvit-logs | 86% | 86% | — | | devvit-skills-setup | 79% | 79% | — | <details> <summary>Changes made to <code>devvit-docs</code></summary> - **Expanded frontmatter description** — listed specific capabilities (search docs, find code examples, explain API usage, retrieve config patterns) instead of just "look up documentation", improving agent trigger specificity - **Fixed filename bug** — `ensure-docs.js` → `ensure-docs.cjs` in the "How It Works" workflow to match the actual script - **Added validation checkpoint** — step to verify `docsRoot` exists and contains `.md` files before searching, with fallback to `repoDir/docs/` - **Added concrete search example** — `find/grep` pattern in the workflow so the agent knows exactly how to search the docs directory </details> I also stress-tested your `devvit-docs` skill against a few real-world task evals and it held up really well on version-specific doc lookups with `--project-dir` detection. 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 @mwood23, just resurfacing this in case it slipped by, let me know if any changes are needed! |
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 @mwood23 👋
the Devvit skills are nicely scoped, especially the docs skill that pulls citations directly from reddit/devvit-docs and the logs skill for quick debugging. The README examples showing exactly when to use each skill make it really easy for agents to pick the right one.
ran your skills through
tessl skill reviewat work and found some targeted improvements fordevvit-docs. Here's the before/after:Changes made to
devvit-docsensure-docs.js→ensure-docs.cjsin the "How It Works" workflow to match the actual scriptdocsRootexists and contains.mdfiles before searching, with fallback torepoDir/docs/find/greppattern in the workflow so the agent knows exactly how to search the docs directoryalso stress-tested your
devvit-docsskill against a few real-world task evals and it held up really well on version-specific doc lookups with--project-dirdetection. 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.