feat: improve mobius-error-id-skill score (59% → 89%)#5
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @eigengravy 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `mobius-error-id-skill`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | mobius-error-id-skill | 59% | 89% | +30% | | sip-flow-skill | 85% | — | unchanged | | architecture-endpoints-skill | 74% | — | unchanged | I picked `mobius-error-id-skill` because it had the most headroom — it's a useful skill that was missing a few structural pieces that help agents select and use it reliably. <details> <summary>Changes made</summary> **Description improvements (biggest impact):** - Added explicit "Use when..." clause with trigger conditions (error codes, response_status fields, call IDs, registration/call failures) - Listed concrete actions: decode error codes (101–5xx), trace call IDs, map HTTP response statuses to root causes - Added natural trigger terms users would say: "Mobius error", "debugging", "response_status", "registration failures" **Content improvements:** - Added "Error ID Formats" section documenting how Mobius errors appear in logs (HTTP status + mobius-error codes, response_status fields, device/call IDs) - Restructured workflow into clear 4-step diagnostic process: extract → look up → report → handle unknowns - Merged redundant "Error Detection and Root Cause Analysis" / "Root Cause Analysis" sub-bullets into a single clear step - Added concrete worked example showing a 503 SERVICE UNAVAILABLE registration failure, the lookup, and the root cause attribution </details> I also stress-tested your `mobius-error-id-skill` against a few real-world task evals and it held up really well on tracing 503 SERVICE UNAVAILABLE registration failures across SSE/CPAPI/Redis dependencies. Kudos for the thorough reference doc. 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 @eigengravy 👋
the multi-agent architecture for log analysis is a smart approach, and breaking the skills into SIP flow, Mobius error identification, and architecture endpoints shows you've mapped the debugging workflow really well.
ran your skills through
tessl skill reviewat work and found some targeted improvements formobius-error-id-skill. Here's the before/after:picked
mobius-error-id-skillbecause it had the most headroom. It's a useful skill that was missing a few structural pieces that help agents select and use it reliably.Changes made
Description improvements (biggest impact):
Content improvements:
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.