feat: improve writing-autests skill score (38% → 92%) - #383
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @bneradt 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for the `writing-autests` skill. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | writing-autests | 38% | 92% | **+54%** | | build-pv | 52% | — | — | | plan-issue | 53% | — | — | | commit | 65% | — | — | | run-autests | 65% | — | — | | review-pr | 67% | — | — | | apply-pr-comments | 68% | — | — | | create-pr | 76% | — | — | | run-unit-tests | 77% | — | — | I picked `writing-autests` because it had the most room for improvement and it's a core skill for the project — AuTests are the backbone of your e2e testing. <details> <summary>Changes made to <code>writing-autests</code></summary> - **Expanded description** with a "Use when..." clause listing concrete trigger scenarios (writing e2e tests, adding replay YAML, updating .test.py files, configuring gold files) - **Added directory structure reference** showing the standard `<test-name>/` layout with `.test.py`, `replay_files/`, and `gold/` subdirectories - **Added a numbered workflow** (6 steps: create dir → write .test.py → create replay YAML → add gold files → run → verify) - **Added a minimal test example** based on real patterns from the repo (using `AddClientProcess`, `AddServerProcess`, `AddProxyProcess`) - **Added replay YAML structure example** showing the `meta`/`sessions`/`transactions` format with `esc_json` encoding - **Documented key extension APIs** (`AddClientProcess`, `AddServerProcess`, `AddProxyProcess`, `Testers.ContainsExpression`, `Testers.ExcludesExpression`) - **Fixed path typo** (`test/autests` → `tests/autests`) - **Cross-referenced** the `run-autests` sibling skill for running tests </details> I also stress-tested your `run-autests` skill against a few real-world task evals and it held up really well on parallel test execution with `autest.sh -j` and selective test filtering with `-f`. 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 @bneradt, just bumping this in case it got lost in the queue, happy to address any feedback! |
Collaborator
I'm sorry, @yogesh-tessl . I'm mortified that I missed this. Thank you for contributing. Looks good. I'll post a review. |
bneradt
requested changes
Aug 11, 2026
|
|
||
| AuTest is an end to end testing framework documented here: | ||
| https://autestsuite.bitbucket.io/ | ||
| AuTest is the end-to-end testing framework for Proxy Verifier. Documentation: https://autestsuite.bitbucket.io/ |
Collaborator
There was a problem hiding this comment.
Jason Kenny, the author of the autest framework, has moved things to github. Can you please update the links? Let's reference both the github repo link and the published doc link:
| └── <name>_proxy.gold | ||
| ``` | ||
|
|
||
| Proxy Verifier extensions are in `tests/autests/gold_tests/autest-site/`. |
Collaborator
There was a problem hiding this comment.
More specifically:
"AuTest framework extensions specific to Proxy Verifier are in..."
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
2 participants
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 @bneradt 👋
truly good work on this. 9 skills covering the full dev loop from planning issues to writing AuTests to building and creating PRs, that's a really complete agent setup. The AGENTS.md is well-structured too, especially the emphasis on backward compatibility and matching existing style.
ran your skills through
tessl skill reviewat work and found some targeted improvements for thewriting-autestsskill. Here's the before/after:picked
writing-autestsbecause it had the most room for improvement and it's a core skill for the project. AuTests are the backbone of your e2e testing.Changes made to
writing-autests<test-name>/layout with.test.py,replay_files/, andgold/subdirectoriesAddClientProcess,AddServerProcess,AddProxyProcess)meta/sessions/transactionsformat withesc_jsonencodingAddClientProcess,AddServerProcess,AddProxyProcess,Testers.ContainsExpression,Testers.ExcludesExpression)test/autests→tests/autests)run-autestssibling skill for running testsquick 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.