feat: improve golang-pro skill score from 94% to 100%#90
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @gorkarevilla 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `golang-pro`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | golang-pro | 94% | 100% | +6% | | golang-performance | 92% | 92% | — | | golang-error-handling | 92% | 92% | — | <details> <summary>What changed in <code>golang-pro</code></summary> - **Quoted frontmatter description** — wrapped the `description` value in quotes for standard YAML formatting - **Tightened persona intro** — replaced the descriptive persona sentence with a direct instruction ("Write idiomatic Go 1.21+ code…") so the agent acts rather than role-plays - **Condensed constraints** — merged the 15-line MUST DO / MUST NOT DO lists into two concise bullet points that retain all the key rules without restating what Go developers and Claude already know - **Removed Output Templates section** — the workflow steps already imply the expected deliverables (interfaces → implementation → tests) - **Removed Knowledge Reference keyword dump** — the terms were already covered by the description, triggers, and reference table, adding no actionable value Net effect: the skill body dropped from 125 to 97 lines while keeping the workflow, code example, reference table, and all constraints intact. </details> I also stress-tested your `golang-pro` skill against a few real-world task evals and it held up really well on concurrent worker pool implementations with context cancellation and error channel propagation. 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 🙏
AI Adoption Report
Per-commit breakdown (1 commits)
Warning The following commits have no Git AI authorship notes — AI adoption cannot be tracked for these changes.
Powered by Git AI Standard v3.0.0 — authorship data from |
Author
|
hey @gorkarevilla, just a gentle nudge in case this got buried, let me know if you need any changes! No rush at all if this is in a review pipeline. |
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 @gorkarevilla 👋
impressive work. Three well-structured Go skills covering performance, error handling, and pro patterns. The fact that you broke them out as separate focused skills rather than one giant doc shows you've thought about how agents actually consume this stuff.
ran your skills through
tessl skill reviewat work and found some targeted improvements forgolang-pro. Here's the before/after:What changed in
golang-prodescriptionvalue in quotes for standard YAML formattingNet effect: the skill body dropped from 125 to 97 lines while keeping the workflow, code example, reference table, and all constraints intact.
also stress-tested your
golang-proskill against a few real-world task evals and it held up really well on concurrent worker pool implementations with context cancellation and error channel propagation. 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.