Skip to content

ci: upgrade to skill-review-and-optimize with /apply-optimize#2

Merged
SnailSploit merged 1 commit into
SnailSploit:mainfrom
yogesh-tessl:ci/upgrade-to-skill-review-and-optimize
May 1, 2026
Merged

ci: upgrade to skill-review-and-optimize with /apply-optimize#2
SnailSploit merged 1 commit into
SnailSploit:mainfrom
yogesh-tessl:ci/upgrade-to-skill-review-and-optimize

Conversation

@yogesh-tessl
Copy link
Copy Markdown
Contributor

@yogesh-tessl yogesh-tessl commented Apr 17, 2026

Thanks for merging the skill review + improvement PR. Really glad to see the workflow live on the repo! 🙏

Claude-Red already has the Tessl skill review workflow from that last PR. This upgrades it to tesslio/skill-review-and-optimize, which adds AI-powered optimization suggestions and a one-click /apply-optimize trigger on top of the existing review feedback.

What's new

Before After
Action tesslio/skill-review tesslio/skill-review-and-optimize
Review scores
AI optimization suggestions
One-click /apply-optimize
How it works

On every PR that touches a SKILL.md:

  1. The action reviews the changed files and posts scores (same as before)
  2. New: it also posts an AI-suggested improved version of each skill in the same comment

To apply the suggestions:

  • Anyone with write access comments /apply-optimize on the PR
  • The skill-optimize-apply.yml workflow commits the improved SKILL.md directly to the PR branch. No copy-paste needed

🔑 One-time setup required

Add a TESSL_API_TOKEN secret to this repo:
Settings → Secrets and variables → Actions → New repository secret

Get a free token at https://tessl.io/account/api-keys.

Without the token the action still posts review scores and feedback, just without the optimisation suggestions.

What stays the same

  • Non-blocking by default - no red CI unless you add fail-threshold
  • Only fires on **/SKILL.md PRs - no noise on other changes
  • Contributors need no Tessl account - only the repo owner needs the API token for optimisation

Why this matters for Claude-Red

Claude-Red is built around decision-tree methodology, not just command lists, which is exactly what makes these 38 skills genuinely useful in practice. As the library expands into more attack surfaces, maintaining that depth and structure consistently across contributor PRs becomes harder to do manually. This workflow gives you and every contributor an instant quality signal and an AI-powered fix. So, the bar that made skills like offensive-fuzzing and offensive-sqli good stays enforced as the library scales.


Since the skill-review action is already running on your PRs. If you ever want to go a step further and auto-optimize skills (not just score them), you can point any agent at this guide and let it do the heavy lifting.

Ping me - @yogesh-tessl (https://github.com/yogesh-tessl) - if you hit any snags. Thanks!

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@SnailSploit SnailSploit merged commit 7621cc5 into SnailSploit:main May 1, 2026
@SnailSploit
Copy link
Copy Markdown
Owner

Thanks for your contributions! appreciated !

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.

2 participants