CtrlK
BlogDocsLog inGet started
Tessl Logo

project-flow-ops

Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-structured, lean operational skill with a clear sequenced workflow, an explicit classification table, and a concrete output template. It earns top marks across conciseness, actionability, workflow clarity, and progressive disclosure.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: short bullets, a compact classification table, and a tight output template with no exposition of concepts Claude already knows, matching the score-3 anchor.

3 / 3

Actionability

Provides concrete instruction guidance — an explicit classification table with state definitions, a copy-paste output-format template, and decision rules like 'Never merge from title, summary, or trust alone; use the full diff'; absence of code is not penalized for this instruction-only skill per scoring notes.

3 / 3

Workflow Clarity

A clearly sequenced 4-step workflow (Read → Classify → Decide Linear → Keep consistent) with the classification table serving as an explicit checkpoint and the output template enforcing completeness, matching the score-3 anchor.

3 / 3

Progressive Disclosure

No bundle files are present and none are needed; the body is well-organized into clear sections, so per the simple-skill scoring note progressive disclosure scores 3.

3 / 3

Total

12

/

12

Passed

Description

85%

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

A strong, specific description with an explicit trigger clause and a distinct GitHub/Linear coordination niche. The only weakness is trigger-term phrasing that uses some internal jargon rather than the most natural user expressions.

Suggestions

Soften jargon in the trigger clause by adding user-natural phrasings, e.g. 'Use when the user wants to triage PRs, clean up the issue backlog, or decide whether something needs a Linear ticket.'

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer' — matching the score-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (triage/link/keep systems consistent) and when via an explicit 'Use when...' trigger clause, matching the score-3 anchor with no cap applied.

3 / 3

Trigger Term Quality

The 'Use when...' clause includes natural terms like 'PR triage' and 'backlog control', but 'GitHub-to-Linear coordination' and 'execution flow' lean toward system jargon and miss common user phrasings, matching the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

A clear niche coordinating two named systems (GitHub + Linear) with distinct triggers makes it unlikely to fire for the wrong skill, matching the score-3 anchor.

3 / 3

Total

11

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.