CtrlK
BlogDocsLog inGet started
Tessl Logo

semaphoreci

Semaphore integration. Manage data, records, and automate workflows. Use when the user wants to interact with Semaphore data.

61

Quality

72%

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/semaphoreci/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 highly actionable with concrete, copy-paste-ready Membrane CLI commands and a clear connection workflow with state-based validation. Its few weaknesses are a mildly redundant opening, a dangling 'Step 2' reference, and all content inlined with no progressive disclosure of detail into reference files.

Suggestions

Remove or trim the opening paragraph explaining what Semaphore/CI-CD is, since Claude already knows this, and merge the redundant 'Popular actions' section into 'Searching for actions'.

Fix the dangling navigation: label the action-search/run section 'Step 2' or remove the 'skip to Step 2' phrasing so the workflow reference resolves.

Consider moving the proxy request flag table and clientAction field reference into a references/ file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly lean executable commands, but the opening paragraph explaining what Semaphore is and the redundant 'Popular actions' section are minor over-explanation that could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Provides copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request) with concrete flags and a JSON input example, matching 'fully executable; copy-paste ready; specific examples cover common cases'.

5 / 5

Workflow Clarity

The install→auth→connect→search→run sequence is clear with state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED, polling, error field), but 'skip to Step 2' references a Step 2 that is never labeled, a minor navigation gap keeping it below 5.

4 / 5

Progressive Disclosure

No bundle files exist; the single-file skill is well-organized with clear section headers and no nested references, though the inline proxy-flag table and clientAction detail could be externalized, fitting 'good structure; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

62%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 third-person and covers both what the skill does and when to use it, anchored to a clearly named platform. Its main weakness is generic action language and a thin trigger-phrase set that omits common Semaphore/CI-CD synonyms.

Suggestions

Replace generic verbs with concrete Semaphore actions, e.g. 'Manage Semaphore projects, workflows, pipelines, and deployments' instead of 'Manage data, records'.

Expand the 'Use when' clause with concrete triggers: 'Use when the user wants to manage Semaphore CI/CD projects, workflows, pipelines, deployments, or secrets.'

Add natural synonyms users say (CI/CD, pipelines, jobs, deployments) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Semaphore domain and enumerates 'Manage data, records, and automate workflows', but the actions are generic rather than concrete, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Answers both 'what' ('Semaphore integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Semaphore data'), but the 'when' clause is generic rather than listing concrete trigger phrases, so it is not a 5.

4 / 5

Trigger Term Quality

Includes the key product term 'Semaphore' plus 'data', 'records', 'workflows', but misses common synonyms like CI/CD, pipelines, or deployments, matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

'Semaphore' is a named platform giving it a clear niche, but the generic 'automate workflows' phrasing leaves minor overlap risk with broad CI/CD skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

14

/

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
membranedev/application-skills
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.