CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-feedback

Retired. Reporting feedback and sharing a session are documented by the CLI itself: run `deepline feedback send --help` and `deepline sessions send --help`. Kept only so installed CLIs that still list this skill keep syncing.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an exemplary retirement stub: it wastes no tokens, gives fully executable commands for every action it mentions, and unambiguously redirects both of its former capabilities to the CLI's own documentation. Judged strictly on what is written against the rubric's simple-skill carve-outs, it is essentially optimal for its purpose.

DimensionReasoningScore

Conciseness

The 22-line body is lean and every token earns its place: a two-line install snippet, one sentence declaring the skill holds no instructions, and two bullets that describe exactly what each --help command covers. There is no padding, no over-explanation, and no concepts Claude already knows.

5 / 5

Actionability

Every piece of guidance is a copy-paste-ready command: 'npm install -g deepline', 'deepline -h', 'deepline feedback send --help', and 'deepline sessions send --help'. The two bullets cover the common cases (reporting feedback, sharing a session) and state what each command explains, fully matching the 'copy-paste ready commands covering common cases' anchor.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines with no multi-step process, and the single action — run the relevant --help command, chosen unambiguously from the two labeled bullets — is clear. The simple-skill exception applies; there are no destructive or batch operations that would require validation steps.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ directories exist), and the body is well-organized with a Quick Start section and clearly labeled bullets. Per the rubric's simple-skill carve-out, this earns a top score on structure alone, with no nested or buried references.

5 / 5

Total

20

/

20

Passed

Description

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

This is a well-written retirement notice: it is honest about the skill's retired status, explains why it still exists ('Kept only so installed CLIs that still list this skill keep syncing'), and redirects to concrete CLI help commands. Its weaknesses are structural for a trigger description — no 'Use when' guidance, limited natural-language keyword coverage, and actions that are documentation pointers rather than capability descriptions.

Suggestions

Add an explicit trigger clause (e.g., 'Use when the user asks about reporting deepline feedback or sharing a deepline session') so Claude knows when this skill applies, which would raise completeness.

Broaden natural keyword coverage with synonyms users would actually say, such as 'send feedback', 'bug report', or 'share a session transcript', to improve trigger term quality.

Briefly state the concrete capabilities being redirected (e.g., 'Sending feedback with evidence and flags; sharing and rating a session transcript') so the description enumerates specific actions rather than only naming the help commands.

DimensionReasoningScore

Specificity

The description names the domain ('Reporting feedback and sharing a session') and two concrete commands ('deepline feedback send --help', 'deepline sessions send --help'), but these are pointers to where documentation lives rather than an enumeration of the skill's capabilities, matching the '1-2 concrete actions, not comprehensive' anchor. It is above anchor 2 because the actions and commands are specific, not generic.

3 / 5

Completeness

The 'what' is clear — the skill is retired and feedback/session-sharing is documented by the CLI itself — but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. This fits the 'clear what, missing when' anchor exactly, not anchor 4 which requires both.

3 / 5

Trigger Term Quality

Natural phrases like 'feedback', 'report', and 'sharing a session' are present and would plausibly be said by a user, but common variations and synonyms ('send feedback', 'bug report', 'share transcript') are missing. This sits squarely at 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The deepline-specific command names ('deepline feedback send', 'deepline sessions send') establish a clear niche with minimal conflict risk, but the generic terms 'feedback' and 'session' create minor overlap risk with other feedback- or session-related skills. This is 'mostly distinct; minor overlap risk' rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

getaero-io/gtm-eng-skills

Path

skills/deepline-feedback/SKILL.md

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.