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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/project-flow-ops/SKILL.md

Quality

Content

68%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.

A well-structured, lean operational skill with concrete classification logic and an explicit output format, but its destructive/batch triage workflow lacks in-sequence validation checkpoints, capping workflow_clarity at 3.

Suggestions

Embed explicit validation checkpoints inside the Core Workflow steps (e.g., 'Before classifying as Merge: verify the full diff and confirm CI is green') so validation is in-sequence rather than only in a separate Review Rules section.

Add one or two concrete tool invocations (e.g., `gh pr view`, `gh pr diff`, a Linear CLI/API call) so the actionable guidance includes copy-paste-ready commands, not just decision criteria.

De-duplicate the Linear-warranted criteria between the 'Operating Model' list and Core Workflow step 3 to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Lean and table/bullet-driven with no generic padding about what GitHub or Linear are; minor redundancy between the 'Operating Model' Linear criteria and Core Workflow step 3 keeps it just below 5.	4 / 5
Actionability	Instruction-only but actionable: a concrete classification table, explicit Linear-creation criteria, review rules, and a copy-paste output template; lacks concrete tool invocations (gh/Linear CLI commands), which is a minor gap.	4 / 5
Workflow Clarity	A clear 4-step sequence exists, but merging/closing PRs is a destructive/batch operation and validation checkpoints live only in a separate 'Review Rules' section rather than as explicit in-sequence checkpoints, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and the single file is well-organized into clear sections with no nested references; at over 50 lines with slight section redundancy it falls just short of the simple-skill 5.	4 / 5
	Total	15 / 20 Passed

Description

87%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.

A strong, third-person description that clearly states both capability and trigger conditions with a distinctive GitHub/Linear coordination niche. Minor specificity and trigger-synonym gaps keep specificity and trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('triaging issues and pull requests', 'linking active work', 'keeping GitHub public-facing while Linear remains the internal execution layer'), though the opening 'Operate execution flow' framing is slightly high-level, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Operate execution flow across GitHub and Linear...') and when ('Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases users would say are present ('backlog control', 'PR triage', 'GitHub-to-Linear coordination'), with good keyword coverage but a few common synonyms missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (dual GitHub/Linear coordination) with distinct triggers ('GitHub-to-Linear coordination', 'PR triage') and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/project-flow-ops/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.