CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

second-opinion

Load for a cross-model review, challenge, audit, or quick consult.

Quality

68%

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 ./.agents/skills/second-opinion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An impressively dense, imperative body with no known-concept padding and genuinely executable command guidance, undermined by run-on Configuration/Error-Handling paragraphs that duplicate the --help contract and by workflow links that dangle — no workflows/ directory ships with the bundle. Tightening the prose into rules-of-thumb plus fixing or inlining the workflow files would raise both conciseness and navigation.

Suggestions

Ship the workflows/ files the table links to (review.md, challenge.md, audit.md, quick.md) or replace the links with inline per-mode steps — as delivered, four of five primary navigation links are broken.

Move the room-check failure taxonomy and configuration-key detail out of Configuration/Error Handling into a reference file (or rely solely on `second-opinion --help`, which the body already delegates to repeatedly), keeping only the decision rules inline.

Break the ~300-word Configuration run-on into a short table or bulleted rules so each rule (env precedence, foreground-cap, room-check, inline-diff) is individually scannable.

DimensionReasoningScore

Conciseness

There is no padding with concepts Claude already knows — every sentence carries skill-specific contract detail — but the Configuration section is a single ~300-word run-on sentence and Error Handling is one dense paragraph whose failure taxonomy duplicates what is already delegated to `second-opinion --help` ('Keys, defaults... : `second-opinion --help`'). This matches 'mostly efficient but... could be tightened' rather than 4, since whole clauses of the room-check taxonomy read like --help content inlined into the skill body.

3 / 5

Actionability

The guidance is concrete and executable: an exact invocation (`.agents/skills/second-opinion/scripts/second-opinion <mode> [options]`), a copy-paste quick-mode example with flags, and unambiguous per-flag rules ('Always pass `--cwd`', 'Pass `--foreground` when the call can outlast the harness foreground cap'). It stays at 4 rather than 5 because the four per-mode workflow files the table points to do not exist in the bundle, so the actual mode-specific steps are not executable from what is shipped.

4 / 5

Workflow Clarity

Execution Rules give a clear ordered procedure — select target from roster, always --cwd, --foreground when long-running, run the printed wait command 'until terminal' — and Error Handling spells out a recovery path per failure mode (refusal, timeout, each room-check variant), which is a real feedback loop. It falls short of 5 because the per-mode sequences live in the referenced workflow files (missing here) rather than being inline with explicit validation checkpoints.

4 / 5

Progressive Disclosure

Structure exists and is clearly signaled — a workflows table with links, one real one-level-deep reference ([references/multi-lane.md](references/multi-lane.md) exists, ~80 lines, no nested references) — but all four workflow links (workflows/review.md, challenge.md, audit.md, quick.md) point to files absent from the bundle, and long configuration/error-taxonomy detail that belongs in a reference file is inlined instead. This sits between 'content that should be separate is inline' (2) and 'most content appropriately placed' (4); the clearly signaled but broken references keep it at 3.

3 / 5

Total

14

/

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.

A concise, honest description with an explicit load trigger and a distinctive cross-model niche, but it is underspecified: the actions lack objects, and it omits the skill's own most natural trigger phrase ("second opinion") plus common synonyms. Adding a 'Use when...' clause with concrete user phrasings would lift completeness and trigger quality.

Suggestions

Include the phrase users most naturally say — e.g. 'Use when the user asks for a second opinion, another model's take, or a critique of pending changes.'

Give the actions objects so they are concrete: 'review pending changes/diffs, audit a path, challenge a design decision' rather than bare mode names.

Add synonyms such as 'critique', 'feedback', or 'sanity check' to widen natural trigger coverage without adding length.

DimensionReasoningScore

Specificity

The description names the domain ("cross-model") and four actions ("review, challenge, audit, or quick consult") via the "Load for a" phrasing, but the actions are terse and lack objects — review/audit of what is never stated, and the argument-hint detail (scope, path, question) lives outside the description. This matches 'names domain and concrete actions, but not comprehensive' rather than 4, whose example lists actions with their objects ('Extracts text from PDF files, fills forms, converts pages to images').

3 / 5

Completeness

"Load for a cross-model review, challenge, audit, or quick consult" provides both a what (the four modes) and an explicit when-equivalent trigger clause ("Load for..."), so it is not capped at 3. It falls short of 5 because the when-clause names modes rather than concrete user situations — compare the 5 anchor's 'when the user mentions PDFs, forms, or document extraction' — leaving when-to-load guidance less specific than it could be.

4 / 5

Trigger Term Quality

It includes several natural terms users would say — "review", "challenge", "audit", "consult" — but misses the most natural phrase of all for this skill, "second opinion", along with common variations like "critique", "feedback", or "sanity check", and "cross-model" itself is jargon a user is unlikely to say. This lands at 'some relevant keywords but missing common variations or synonyms' rather than 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

"Cross-model" carves out a clear niche (consulting an external, different AI CLI) that ordinary review/audit skills do not occupy, giving minimal conflict risk on that axis. It stays at 4 rather than 5 because the bare terms "review" and "audit" still overlap with code-review and security-review skills when the cross-model aspect is not what the user has in mind.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 4 possibly missing (workflows/audit.md, workflows/challenge.md, workflows/quick.md, workflows/review.md)

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/second-opinion/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.