Skip to content

feat: improve content-pipeline skill score (86% → 92%)#3

Open
rohan-tessl wants to merge 2 commits into
OrangeViolin:mainfrom
rohan-tessl:improve/skill-review-optimization
Open

feat: improve content-pipeline skill score (86% → 92%)#3
rohan-tessl wants to merge 2 commits into
OrangeViolin:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl

Copy link
Copy Markdown

Hey @OrangeViolin 👋

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
content-pipeline 86% 92% +6%

This PR covers your 1 skill in the repo. I kept changes focused and non-breaking — only the single SKILL.md was in scope.

What changed in content-pipeline
  • Description enhanced with an explicit "Use when..." clause and bilingual (Chinese + English) trigger terms for better agent discovery
  • Added user-invocable: true and triggers array with 15 natural trigger keywords for frontmatter compliance
  • Moved ethics reasoning ("为什么要诚实" + prohibited/correct examples) to references/honesty-principles.md — kept the quick-reference labeling template inline
  • Moved brand color tables (01fish墨绿 + 鱼头头桃粉 full palettes, selection rules, font/badge specs) to references/brand-colors.md — kept a concise summary inline
  • Fixed podcast output count — listed "三样" (3) but enumerated 5 items; corrected to "五样"
  • Updated reference index to include the two new reference files

Tessl Skill Review GitHub Action ✅

I've also included a GitHub Action (.github/workflows/skill-review.yml) that automatically reviews any SKILL.md changed in future PRs and posts scores as a PR comment.

What this gives you:

  • 🔍 Automatic tessl skill review runs on every PR touching SKILL.md
  • 💬 One updated PR comment with scores and improvement feedback
  • 🔓 Zero extra accounts — contributors don't need a Tessl login; only GITHUB_TOKEN is used
  • Non-blocking by default — feedback-only, no surprise red CI (add fail-threshold: 70 later if you want a hard gate)
  • 📈 Covers future skills incrementally as contributors edit them

Want automatic AI optimization on every SKILL.md change? 🚀

The action I've added gives you review scores on PRs. We also have a more powerful variant — tesslio/skill-review-and-optimize — that can:

  • Run AI-powered optimization suggestions on every SKILL.md PR (requires adding TESSL_API_TOKEN as a repo secret)
  • Let contributors accept suggested improvements by commenting /apply-optimize
  • Still works in review-only mode with zero secrets

Interested? Tick the box and I'll raise a follow-up PR:

  • Yes please! Add the tesslio/skill-review-and-optimize action so every SKILL.md PR gets AI optimization suggestions + the /apply-optimize flow
  • No thanks — the review scores action is enough for now

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 — @rohan-tessl — if you hit any snags.

Thanks in advance 🙏

Hey @OrangeViolin 👋

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 |
|-------|--------|-------|--------|
| content-pipeline | 86% | 92% | +6% |

This PR covers your 1 skill in the repo. I kept changes focused and non-breaking — only the single SKILL.md was in scope.

<details>
<summary>What changed in content-pipeline</summary>

- **Description enhanced** with an explicit "Use when..." clause and bilingual (Chinese + English) trigger terms for better agent discovery
- **Added `user-invocable: true`** and **`triggers`** array with 15 natural trigger keywords for frontmatter compliance
- **Moved ethics reasoning** ("为什么要诚实" + prohibited/correct examples) to `references/honesty-principles.md` — kept the quick-reference labeling template inline
- **Moved brand color tables** (01fish墨绿 + 鱼头头桃粉 full palettes, selection rules, font/badge specs) to `references/brand-colors.md` — kept a concise summary inline
- **Fixed podcast output count** — listed "三样" (3) but enumerated 5 items; corrected to "五样"
- **Updated reference index** to include the two new reference files

</details>

## Tessl Skill Review GitHub Action ✅

I've also included a GitHub Action (`.github/workflows/skill-review.yml`) that automatically reviews any `SKILL.md` changed in future PRs and posts scores as a PR comment.

**What this gives you:**
- 🔍 Automatic `tessl skill review` runs on every PR touching `SKILL.md`
- 💬 One updated PR comment with scores and improvement feedback
- 🔓 **Zero extra accounts** — contributors don't need a Tessl login; only `GITHUB_TOKEN` is used
- ✅ **Non-blocking by default** — feedback-only, no surprise red CI (add `fail-threshold: 70` later if you want a hard gate)
- 📈 Covers future skills incrementally as contributors edit them

## Want automatic AI optimization on every SKILL.md change? 🚀

The action I've added gives you **review scores** on PRs. We also have a more powerful variant — [`tesslio/skill-review-and-optimize`](https://github.com/tesslio/skill-review-and-optimize) — that can:

- Run **AI-powered optimization suggestions** on every `SKILL.md` PR (requires adding `TESSL_API_TOKEN` as a repo secret)
- Let contributors accept suggested improvements by commenting **`/apply-optimize`**
- Still works in review-only mode with zero secrets

Interested? Tick the box and I'll raise a follow-up PR:

- [ ] **Yes please!** Add the `tesslio/skill-review-and-optimize` action so every SKILL.md PR gets AI optimization suggestions + the `/apply-optimize` flow
- [ ] **No thanks** — the review scores action is enough for now

---

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
rohan-tessl marked this pull request as ready for review April 21, 2026 08:53
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