feat: improve skill review scores and add Tessl CI workflow

[rohan-tessl]

Hey @stefanprodan 👋

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
commit-assisted-by	17%	90%	+73%
gitops-knowledge	89%	94%	+5%
gitops-cluster-debug	94%	94%	0%
gitops-repo-audit	94%	94%	0%
flux-controller-patch-releases	97%	97%	0%

This PR covers all 5 skill(s) in the repo. I respected the conventions in AGENTS.md — keeping SKILL.md concise with heavy content in references/, and maintaining the explicit step-by-step workflow style. Description format was standardized to quoted strings across all skills.

What changed in commit-assisted-by

• Fixed validation-blocking description — the <agent-name>/<model-id> angle bracket syntax was flagged as XML tags by validators, causing the skill to fail deterministic checks (17% score). Rephrased to parenthetical notation (agent-name/model-id) while preserving the same meaning
• Converted description from YAML block scalar (>) to a quoted string for frontmatter compliance

What changed in gitops-knowledge

• Trimmed verbose "What is Flux" intro — removed generic GitOps definition that Claude already knows, kept Flux-specific behavioral details
• Condensed reconciliation loop — tightened from 4 verbose paragraphs to 4 lean, action-focused bullet points
• Added validation checkpoints to the "How to Set Up GitOps from Scratch" workflow — explicit kubectl verification steps after FluxInstance and Kustomization creation (fixes workflow_clarity score from 2/3 → 3/3)
• Added schema validation feedback loop — explicit "validate output against schema, fix errors, re-validate" instruction in the Rules section
• Converted description from YAML block scalar (>) to a quoted string

What changed in gitops-cluster-debug, gitops-repo-audit, flux-controller-patch-releases

• Converted descriptions from YAML block scalar (>) to quoted strings for frontmatter compliance — no content changes, these skills already scored 94–97%

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

This workflow complements the existing publish.yml, release.yaml, and update-schemas.yaml pipelines — it only reviews skill markdown on PRs and does not replace any build or release workflow.

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 🙏