feat: improve skill scores for k0ntext

[rohan-tessl]

Hey @Yoshikemolo 👋

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
orchestration	68%	96%	+28%
test-execution	69%	100%	+31%
devflow-planning	71%	94%	+23%
pr-creation	77%	100%	+23%
git-jira-integration	82%	100%	+18%

This PR is intentionally scoped to five skills to keep it reviewable — the remaining three skills (jira-read 89%, jira-write 88%, git-operations 83%) can be improved in follow-ups or via automated review on future PRs.

Changes summary

orchestration (68% → 96%)

• Rewrote description with natural trigger terms (pipeline, batch operations, retry) and explicit "Use when" clause
• Added concrete JSON state tracking schema showing how execution progress is recorded
• Restructured workflow into clear 4-phase sequence with validation checkpoints
• Enhanced error handling table with "Next Step" column for feedback loops
• Added rollback params to plan YAML example

test-execution (69% → 100%)

• Expanded description with trigger terms (test suite, code coverage, failing tests) and "Use when" clause
• Added explicit 5-step workflow: run → check exit code → review failures → verify coverage → report
• Replaced generic failure handling with concrete example showing real test output and actionable diagnosis
• Removed low-value "Example Usage" and "Output Format" sections

devflow-planning (71% → 94%)

• Added rich trigger terms (story points, backlog grooming, burndown trends, sprint capacity, team velocity)
• Made sprint planning workflow concrete with formulas inline and validation checkpoint (step 5)
• Removed generic Scrum knowledge Claude already has (acceptance criteria, etc.)
• Condensed GitFlow section and removed redundant Example Usage section

pr-creation (77% → 100%)

• Added trigger terms (PR, pull request, code review) to description with "Use when" clause
• Replaced vague example usage with concrete 4-step workflow using executable gh CLI commands
• Removed low-value "Linking" section
• Added verification steps (check ahead_by, confirm creation with gh pr view)

git-jira-integration (82% → 100%)

• Added explicit "Use when" clause with natural trigger scenarios
• Added expected output/response format for all tool calls (success and failure cases)
• Added feedback loop to commit validation: if invalid, fix per errors and re-validate before committing
• Enriched workflow steps with action guidance after each tool invocation

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 🙏