feat: improve stream-cli skill score (91% to 97%)#20
Open
rohan-tessl wants to merge 1 commit into
Open
Conversation
Hey @vaneenige 👋 really like how transparent the README is about what gets installed. That audit table listing every network-touching step with source links is the kind of thing most skill packs don't bother with. 8 skills covering the full Stream stack from CLI operations to platform-specific scaffolding for Swift, Android, RN, and Flutter, that's solid coverage. 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 | |-------|--------|-------|--------| | stream-cli | 91% | 97% | +6% | | stream | 92% | 92% | 0% | | stream-docs | 16% | 16% | 0% | | stream-builder | 85% | 85% | 0% | | stream-swift | 92% | 92% | 0% | | stream-android | 17% | 17% | 0% | | stream-react-native | 92% | 92% | 0% | | stream-flutter | 92% | 92% | 0% | `stream-cli` had the most headroom among your passing skills so I focused there. <details> <summary>Changes made</summary> **stream-cli (+6%)**: - Removed the redundant "CLI Rules (summary)" section at the end of SKILL.md, which restated all six points already covered in the CLI Workflow section above it (endpoint discovery, help flags, lazy auth, missing params, safe mode, summarization) - This eliminated token waste without losing any information, since every rule in the summary was already present in the workflow steps and exit code recovery table - Content conciseness score improved from 2/3 to 3/3, bringing the overall score from 91% to 97% - Net change: 9 lines removed, 0 lines added </details> I also stress-tested your `stream-cli` skill against a few real-world task evals and it held up really well on safe mode refusal recovery for mutating endpoints (the exit code 5 flow with user notification before retry). Solid design. 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 @rohan-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 @vaneenige 👋
really like how transparent the README is about what gets installed. That audit table listing every network-touching step with source links is the kind of thing most skill packs don't bother with. 8 skills covering the full Stream stack from CLI operations to platform-specific scaffolding for Swift, Android, RN, and Flutter, that's solid coverage.
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:stream-clihad the most headroom among your passing skills so I focused there.Changes made
stream-cli (+6%):
I also stress-tested your
stream-cliskill against a few real-world task evals and it held up really well on safe mode refusal recovery for mutating endpoints (the exit code 5 flow with user notification before retry). Solid design.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 @rohan-tessl, if you hit any snags.
Thanks in advance 🙏