Skip to content

feat: optimize 3 skills — solidity, battlechain, battlechain-tutorial#10

Open
rohan-tessl wants to merge 1 commit intoCyfrin:mainfrom
rohan-tessl:improve/skill-review-optimization
Open

feat: optimize 3 skills — solidity, battlechain, battlechain-tutorial#10
rohan-tessl wants to merge 1 commit intoCyfrin:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link
Copy Markdown

@rohan-tessl rohan-tessl commented Apr 24, 2026

Hullo @PatrickAlphaC 👋

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

Skill Review Score Card

Skill Before After Change
solidity 68% 93% +25%
battlechain 90% 93% +3%
battlechain-tutorial 64% 93% +29%
Changes summary

solidity (68% → 93%)

  • Description: Expanded with specific concrete actions (Foundry workflows, security patterns, gas optimization, testing strategies) and natural trigger terms (Solidity, EVM, ERC-20, ERC-721, DeFi, .sol files, Ethereum mainnet, Hardhat)
  • Development Workflow: Added an end-to-end workflow section (Write → Lint → Static Analysis → Test → Audit → Deploy) with explicit validation checkpoints between each step
  • Progressive disclosure: Extracted the branching tree technique into BRANCHING-TREE.md and governance patterns into GOVERNANCE.md — keeps SKILL.md focused while preserving all content
  • Gas and Style Checklist: Consolidated 8 short one-liner tips into a compact checklist format
  • Trimmed redundancy: Removed explanatory phrasing Claude already knows, tightened blog post references

battlechain (90% → 93%)

  • Description: Made lifecycle action more concrete ("deploy → attack mode → promotion to mainnet"), added "contract verification" as trigger term, removed behavioral parenthetical
  • Deployment Lifecycle: Added a 7-step end-to-end lifecycle section with cast call verification checkpoints between critical steps (deploy, create agreement, request attack mode)
  • Removed placeholder: Removed empty "Hardhat — Coming soon" section
  • Tightened intro: Condensed the "What is BattleChain" heading into a single-line description

battlechain-tutorial (64% → 93%)

  • Description: Expanded from vague "prepare projects for BattleChain deployment" to specific actions (scans Foundry contracts/scripts, gathers deployment parameters, generates deployment scripts, Safe Harbor agreements, attack mode requests) with domain trigger terms
  • Progressive disclosure: Extracted the 15-question flow into QUESTIONS.md and Solidity script templates/constants into TEMPLATES.md — reduced SKILL.md from 368 to 165 lines while preserving all content
  • Question summary table: Replaced inline question details with a concise reference table of all 15 questions
  • Condensed AskUserQuestion pattern: Moved repeated tool usage instructions to a shared section in QUESTIONS.md

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 and ask it to optimize your skill. Ping me - @popey - if you hit any snags.

Thanks in advance 🙏

Hullo @PatrickAlphaC 👋

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

![Skill Review Score Card](score_card.png)

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| solidity | 68% | 93% | +25% |
| battlechain | 90% | 93% | +3% |
| battlechain-tutorial | 64% | 93% | +29% |

<details>
<summary>Changes summary</summary>

### solidity (68% → 93%)

- **Description**: Expanded with specific concrete actions (Foundry workflows, security patterns, gas optimization, testing strategies) and natural trigger terms (Solidity, EVM, ERC-20, ERC-721, DeFi, .sol files, Ethereum mainnet, Hardhat)
- **Development Workflow**: Added an end-to-end workflow section (Write → Lint → Static Analysis → Test → Audit → Deploy) with explicit validation checkpoints between each step
- **Progressive disclosure**: Extracted the branching tree technique into `BRANCHING-TREE.md` and governance patterns into `GOVERNANCE.md` — keeps SKILL.md focused while preserving all content
- **Gas and Style Checklist**: Consolidated 8 short one-liner tips into a compact checklist format
- **Trimmed redundancy**: Removed explanatory phrasing Claude already knows, tightened blog post references

### battlechain (90% → 93%)

- **Description**: Made lifecycle action more concrete ("deploy → attack mode → promotion to mainnet"), added "contract verification" as trigger term, removed behavioral parenthetical
- **Deployment Lifecycle**: Added a 7-step end-to-end lifecycle section with `cast call` verification checkpoints between critical steps (deploy, create agreement, request attack mode)
- **Removed placeholder**: Removed empty "Hardhat — Coming soon" section
- **Tightened intro**: Condensed the "What is BattleChain" heading into a single-line description

### battlechain-tutorial (64% → 93%)

- **Description**: Expanded from vague "prepare projects for BattleChain deployment" to specific actions (scans Foundry contracts/scripts, gathers deployment parameters, generates deployment scripts, Safe Harbor agreements, attack mode requests) with domain trigger terms
- **Progressive disclosure**: Extracted the 15-question flow into `QUESTIONS.md` and Solidity script templates/constants into `TEMPLATES.md` — reduced SKILL.md from 368 to 165 lines while preserving all content
- **Question summary table**: Replaced inline question details with a concise reference table of all 15 questions
- **Condensed AskUserQuestion pattern**: Moved repeated tool usage instructions to a shared section in QUESTIONS.md

</details>

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 - [@popey](https://github.com/popey) - if you hit any snags.

Thanks in advance 🙏
@rohan-tessl rohan-tessl marked this pull request as ready for review April 24, 2026 07:09
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