CtrlK
BlogDocsLog inGet started
Tessl Logo

harness

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

56

Quality

64%

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/harness/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 executable Membrane CLI commands and a well-checked connection workflow, but it is padded by a flat 54-item module dump and lacks any progressive disclosure via separate reference files.

Suggestions

Move the 54-item Harness Overview list into a references file (e.g. references/modules.md) and link to it, removing the 'Next Gen' duplicate noise.

Remove the redundant 'Popular actions' action-list command that duplicates the 'Searching for actions' section.

Label the referenced 'Step 2' explicitly or restructure the connection→search→run flow into a numbered sequence with clear validation checkpoints.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but it includes a 54-item flat module dump (much of it 'Next Gen' duplicates) and repeats the action-list command in 'Popular actions', matching 'mostly efficient but includes some unnecessary/padded content that could be tightened.'

3 / 5

Actionability

It provides copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) plus a flags table, fully executable and covering the common cases with clearly-parameterized placeholders.

5 / 5

Workflow Clarity

The connection flow has a clear sequence with explicit state checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll→retry feedback loop, but it references an unlabeled 'Step 2' and lacks an explicit end-to-end connection→action sequence, matching 'clear sequence with most checkpoints; minor validation gaps.'

4 / 5

Progressive Disclosure

Section headers give structure, but no bundle/reference files exist and the large module list is inlined rather than split into a reference, matching 'some structure but content that should be separate is inline' with no signaled one-level references.

3 / 5

Total

15

/

20

Passed

Description

57%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 correctly includes an explicit 'Use when...' trigger and names a clear product niche, but its capability verbs are generic and it omits the natural trigger terms (pipelines, deployments) that would make it more specific and discoverable.

Suggestions

Replace generic verbs with concrete Harness actions, e.g. 'Manage Harness pipelines, deployments, executions, and connectors' to lift specificity.

Add natural trigger terms users say, e.g. 'Use when the user mentions Harness pipelines, deployments, executions, or wants to interact with Harness data.'

Tighten the 'when' clause to reference concrete Harness objects so the trigger is unambiguous.

DimensionReasoningScore

Specificity

It names the domain ('Harness integration') but the actions — 'Manage data, records, and automate workflows' — are minimal and generic verbs rather than concrete operations, matching the anchor for naming a domain with minimal/generic actions.

2 / 5

Completeness

It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Harness data'), but the 'when' could be more specific, matching the both-present-but-could-be-more-explicit anchor.

4 / 5

Trigger Term Quality

'Harness' and 'Harness data' are relevant natural keywords, but the trigger misses common variations a user would say (pipelines, deployments, executions, connectors), matching 'some relevant keywords but missing common variations.'

3 / 5

Distinctiveness Conflict Risk

'Harness integration' targets a named product niche with distinct triggers, giving mostly-distinct identity; minor overlap risk remains because the described actions (manage data, automate workflows) are generic, so it fits 'mostly distinct; minor overlap risk.'

4 / 5

Total

13

/

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.