CtrlK
BlogDocsLog inGet started
Tessl Logo

dev-workflow

The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Ensures agents follow the correct sequence of steps.

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

82%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 well-structured, highly actionable workflow reference with concrete commands, a clear staged sequence, and a validation gate via staging. It is mostly lean and well-organized, with only minor conciseness and feedback-loop gaps.

DimensionReasoningScore

Conciseness

An efficient reference doc with commands in tables and code blocks and minimal padding; every section earns its place, though the 10-item 'Smoke Test Coverage' list and staging credentials could be trimmed slightly.

4 / 5

Actionability

Fully executable guidance: exact `make` targets, URLs, credentials, command tables with scope, and concrete commit-message examples — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

A clear four-stage sequence (Local Dev → Testing → Staging → PR) with staging as an explicit 'pre-PR validation' checkpoint and a troubleshooting table, though explicit 'only proceed when valid' feedback loops are only implied by the staging gate.

4 / 5

Progressive Disclosure

Well-organized into clear section headers with one-level-deep, clearly signaled external references ('See docs/13-parallel-workflow.md for full details'); no nested references and content appropriately inline for an overview, with minor room to split smoke-test detail out.

4 / 5

Total

17

/

20

Passed

Description

66%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 clearly states what the skill covers across four workflow stages and is well-scoped to SkillHub contributors, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding concrete trigger phrases would raise the completeness and trigger-term scores.

Suggestions

Add an explicit 'Use when...' clause naming trigger situations (e.g., 'Use when starting local development, running tests, validating against staging, or preparing a pull request for SkillHub').

Include common synonyms a contributor might say ('build', 'CI', 'commit', 'worktree') to broaden trigger-term coverage.

Drop the meta sentence 'Ensures agents follow the correct sequence of steps' in favor of concrete trigger phrasing.

DimensionReasoningScore

Specificity

Names the domain ('SkillHub contributors') and lists several concrete actions — 'local dev, staging validation, testing, and PR creation' — giving multi-stage coverage, though the actions are workflow stages rather than granular operations.

4 / 5

Completeness

The 'what' is clear (the four workflow stages), but there is no explicit 'Use when...' trigger clause; 'Ensures agents follow the correct sequence of steps' only weakly implies 'when', capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural contributor phrases ('local dev', 'testing', 'staging validation', 'PR creation') a user would say, but misses common synonyms like 'build', 'CI', or 'commit'.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'SkillHub contributors' with distinct triggers (staging validation, PR creation), giving a clear niche with only minor overlap risk from generic dev terms like 'testing'.

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

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

15

/

16

Passed

Repository
iflytek/skillhub
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.