Skip to content

feat: improve alchemy-agentic-gateway skill score#28

Open
yogesh-tessl wants to merge 1 commit into
ProjectOpenSea:mainfrom
yogesh-tessl:improve/skill-review-optimization
Open

feat: improve alchemy-agentic-gateway skill score#28
yogesh-tessl wants to merge 1 commit into
ProjectOpenSea:mainfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl
Copy link
Copy Markdown

Hey @ProjectOpenSea 👋

impressive. The decision tree at the top of the README is a great touch. Five skills covering API queries, marketplace trading, swaps, wallet signing, and tool gating, all following the Agent Skills spec. Really well structured.

also ran your skills through tessl skill review at work and found some targeted improvements for alchemy-agentic-gateway. Here's the full before/after:

Skill Before After Change
alchemy-agentic-gateway 78% 91% +13%
Changes made to `alchemy-agentic-gateway`
  • Added explicit "Use when..." clause to the frontmatter description with natural trigger keywords (keyless, x402, MPP, no API key, autonomous agents) - helps agent frameworks select the right skill automatically
  • Added a quick-start code example (x402 + EVM wallet) directly in the SKILL.md so it has standalone actionability before the protocol rule files are loaded
  • Consolidated three overlapping routing sections (scope_in, scope_out, and "Handing off to other skills") into a single unified routing table - removes redundancy while preserving all handoff guidance
  • Merged "Alchemy-first rule", "Forbidden optimizations", and "Hard requirements" into a single concise "Operating rules" section - same constraints, fewer tokens

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.

Hey @ProjectOpenSea 👋

I ran your skills through `tessl skill review` at work and found some targeted improvements for `alchemy-agentic-gateway`. Here's the full before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| opensea | 91% | 91% | — |
| opensea-api | 82% | 82% | — |
| opensea-marketplace | 85% | 85% | — |
| opensea-swaps | 81% | 81% | — |
| opensea-wallet | 86% | 86% | — |
| opensea-tool-sdk | 92% | 92% | — |
| alchemy-cli | 89% | 89% | — |
| alchemy-mcp | 89% | 89% | — |
| **alchemy-agentic-gateway** | **78%** | **91%** | **+13%** |
| alchemy-api | 92% | 92% | — |

<details>
<summary>Changes made to `alchemy-agentic-gateway`</summary>

- Added explicit "Use when..." clause to the frontmatter description with natural trigger keywords (keyless, x402, MPP, no API key, autonomous agents) — helps agent frameworks select the right skill automatically
- Added a quick-start code example (x402 + EVM wallet) directly in the SKILL.md so it has standalone actionability before the protocol rule files are loaded
- Consolidated three overlapping routing sections (scope_in, scope_out, and "Handing off to other skills") into a single unified routing table — removes redundancy while preserving all handoff guidance
- Merged "Alchemy-first rule", "Forbidden optimizations", and "Hard requirements" into a single concise "Operating rules" section — same constraints, fewer tokens

</details>

I also stress-tested your `alchemy-agentic-gateway` skill against a few real-world task evals and it held up really well on x402 payment-flow routing between EVM and Solana wallets with SIWE/SIWS 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](https://github.com/yogesh-tessl) — if you hit any snags.

> Note: I understand this repo is a read-only mirror synced from your internal monorepo. If the change looks good, feel free to recreate it internally — happy to have it land however works best for your workflow.

Thanks in advance 🙏
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant