feat: improve api-setup skill score from 39% to 93%#35
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @angiejones 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `api-setup`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | api-setup | 39% | 93% | +54% | | beads | 73% | — | — | | code-review | 40% | — | — | | frontend-design | 66% | — | — | | goose-blog-post | 62% | — | — | | rp-why | 33% | — | — | | testing-strategy | 39% | — | — | <details> <summary>What changed in api-setup</summary> - Description: Expanded from a vague one-liner to a specific description with concrete actions (scaffold, generate config, set up auth, verify connection) and a Use when... clause with natural trigger terms - Workflow steps: Each step now includes copy-paste-ready commands (./setup.sh, python3 -m json.tool, curl connection test) instead of abstract instructions - Integrated validation: JSON syntax validation is now a gated step before testing the connection, rather than a post-hoc checklist - Config example: Added an inline JSON config example so the agent can see the exact structure without needing to open the template file - Bundle file references: Added explicit links to setup.sh and templates/config.template.json for progressive disclosure - Removed generic troubleshooting: Stripped basic advice that any agent already knows — keeps the skill focused on project-specific guidance - Added tags: rest and configuration for better marketplace discoverability </details> I also stress-tested your api-setup skill against a few real-world task evals and it held up really well on scaffolding a multi-endpoint REST integration with Bearer token auth. 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 — if you hit any snags. --- Submit a Skill Skill Info - Skill name (folder name): api-setup - Short description: Scaffold a new REST API integration by generating a config file, setting up authentication, and verifying the connection - Author / handle: goose (original) / @yogesh-tessl (improvements) - Version: 1.0 Structure Checklist - [x] Skill is in a top-level folder (api-setup/) - [x] The folder contains a SKILL.md file - [x] SKILL.md includes valid YAML frontmatter (name, description, author, version, tags) - [x] Supporting files (scripts/templates) live inside the skill folder Security Acknowledgement - [x] This skill does not contain malicious behavior - [x] This skill does not attempt to exfiltrate secrets, tokens, or credentials - [x] This skill does not contain obfuscated payloads - [x] I understand that all submissions run through automated security scanning - [x] I understand this PR may be rejected if it fails validation or security review Additional Notes This PR only modifies api-setup/SKILL.md — no changes to supporting files (setup.sh, templates/). The diff is intentionally small (77 lines) to make review quick and painless. Thanks in advance 🙏
✅ Validate Skills — PASSEDSummary: FAIL=0 · WARN=0 Output (last 200 lines) |
🛡️ Skills Security Scan — WARNSummary: FAIL=0 · WARN=3 · FILES=3
|
Author
|
hey @angiejones, just bumping this in case it got lost in the queue, happy to address any feedback! |
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 @angiejones 👋
ran your skills through
tessl skill reviewat work and found some targeted improvements forapi-setup. Here's the before/after:What changed in api-setup
also stress-tested your
api-setupskill against a few real-world task evals and it held up really well on scaffolding a multi-endpoint REST integration with Bearer token auth. 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.