feat: improve skill quality scores across all plugins

[rohan-tessl]

Hey 👋 @fcakyon

I ran your skills through tessl skill review at work and found some targeted improvements.

Here's the full before/after:

Skill	Before	After	Change
paper-search-usage	37%	94%	+57%
slack-usage	36%	86%	+50%
playwright-testing	51%	96%	+45%
mongodb-setup	59%	94%	+35%
tavily-setup	65%	100%	+35%
linear-usage	51%	83%	+32%
gcloud-usage	59%	90%	+31%
pr-comment-workflow	63%	94%	+31%
supabase-setup	55%	86%	+31%
tavily-usage	55%	86%	+31%
ccproxy-setup	66%	94%	+28%
pr-workflow	66%	94%	+28%
mongodb-usage	55%	83%	+28%
azure-setup	59%	86%	+27%
commit-workflow	59%	86%	+27%
linear-setup	59%	86%	+27%
slack-setup	59%	86%	+27%
github-dev-setup	69%	94%	+25%
azure-usage	63%	86%	+23%
gcloud-setup	72%	94%	+22%
paper-search-setup	59%	81%	+22%
statusline-setup	69%	86%	+17%
supabase-usage	73%	86%	+13%

Changes made

Across all 23 skills:

• Converted all frontmatter descriptions to quoted string format with specific, action-oriented language
• Added "Use when..." trigger clauses with natural search terms users would actually type
• Structured setup workflows into numbered steps for progressive disclosure
• Replaced bullet-list troubleshooting with structured Error/Cause/Fix tables
• Added concrete, executable code examples where missing
• Removed redundant sub-headings and consolidated overlapping sections
• Used collapsible
  Details

  blocks for reference material (channel types, MCP limitations, etc.)
• Preserved all domain expertise, specialized terminology, and existing code examples

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

Thanks in advance 🙏

[rohan-tessl]

Hey,

I noticed this skill improvement PR got closed — totally fair, I clearly missed something on what you actually need from contributions.

Would you be open to a quick 15-min chat so I can understand your standards better? The changes covered 23 skills with improvements like structured setup workflows, error/cause/fix tables, and better trigger clauses — so I'd love to know if the approach didn't fit your vision for the repo, or if there's a better way to contribute.

The goal is to ensure future contributions save time, deliver value to the open-source community, and are made in a thoughtful and effective way.

Happy to send over a voucher at your favourite coffee place: Grab a slot here