CtrlK
BlogDocsLog inGet started
Tessl Logo

github-workflow

Install and operate a full GitHub issue-to-merge workflow for any repository using event-driven and cron missions. Handles issue planning, PR monitoring, CI fixing, staging review, and post-merge learning.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/github-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-structured overview with an explicit validation/feedback loop and a clearly signaled one-level-deep reference; its only gap is that template payloads live in the reference rather than inline.

DimensionReasoningScore

Conciseness

The body is lean and efficient, assuming Claude's competence — it never explains what GitHub, webhooks, or CI are, and every section earns its tokens, matching the 5 anchor.

5 / 5

Actionability

Concrete guidance names specific tools and calls (mission_create, mission_list, event_emit, named missions with cadence patterns), but the actual template payloads are deferred to the reference file rather than shown inline, leaving a minor gap versus copy-paste-ready 5.

4 / 5

Workflow Clarity

Install Procedure and Validation sections give a clear sequence with explicit validation checkpoints and a feedback loop (synthetic event_emit, confirm a mission fired, check status, confirm no unrelated missions fired), satisfying the 5 anchor for an install/batch operation.

5 / 5

Progressive Disclosure

The body is an overview that defers detailed templates to a clearly signaled, one-level-deep, real reference (references/workflow-routines.md) and is itself well-organized into navigable sections, matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Description

63%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinguishes a clear niche, but it omits an explicit "Use when..." trigger clause and frames terms as capabilities rather than natural user phrases, capping completeness and trigger quality.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., "Use when automating issue-to-merge workflows, CI fixing, or PR monitoring for a GitHub repo").

Reframe capability nouns as user-facing trigger terms and include common synonyms/extensions (e.g., "GitHub PRs", "CI/CD", ".github") to lift trigger term quality.

Tighten distinctiveness by leading with the unique angle (event-driven + cron mission installation) before the generic "GitHub workflow" framing.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "issue planning, PR monitoring, CI fixing, staging review, and post-merge learning" — giving comprehensive coverage rather than the minor gaps that would warrant a 4.

5 / 5

Completeness

There is a clear "what" (install and operate an issue-to-merge workflow) but no "Use when..." clause or explicit trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The description mentions relevant terms (GitHub, issue, PR, CI, merge) but phrases them as capabilities rather than natural user trigger phrases, and lacks synonyms/extensions; not the broad natural-term coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The niche is specific (event-driven/cron issue-to-merge automation) and largely distinct, though "GitHub workflow/automation" wording carries minor overlap risk with a generic github skill, fitting the 4 anchor better than the 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nearai/ironclaw
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.