CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crossframe-review

Reference-only CrossFrame archive with a local evidence-review fallback; upstream suite execution and source-fidelity certification are unavailable.

Quality

57%

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

Quality

Content

52%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 establishes a clear packaging boundary and a well-sequenced, verifiable 5-step evidence-review workflow with reasonable conciseness. Its main weaknesses are repeated boundary disclaimers that pad the token budget, missing execution details (no examples or report format), and a broken file structure: the four substantive reference files are never linked while the body cites nonexistent external paths.

Suggestions

Link the existing bundle files where they belong in the workflow, e.g. "Classify failures using [failure-taxonomy.md](references/failure-taxonomy.md)" and "Score the output with [review-rubric.md](references/review-rubric.md)".

Remove or correct the dead references (UPSTREAM.md, ../../../scripts/agent-rule-policy.json, ../code-review-excellence/SKILL.md) so navigation matches the actual bundle layout.

Consolidate the four repeated upstream-fidelity disclaimers into a single boundary statement and add a brief output template for step 5's report (scope, confirmed issues, uncertain points, repairs, next observation).

DimensionReasoningScore

Conciseness

The body is mostly terse and assumes Claude's competence, but the upstream-fidelity disclaimer recurs four times ("Do not... claim CrossFrame v5 source fidelity", "State that upstream routing, source continuity and v5 fidelity were not verified", "Do not reuse an upstream grade as proof of correctness") alongside packaging meta-commentary. It could be tightened into a single boundary statement, so it does not reach anchor 4.

3 / 5

Actionability

The 5-step procedure gives concrete directives ("Separate observed facts, interpretations, assumptions and missing evidence", "Provide a specific repair with its source location"), but there are no worked examples, no output format for the final report, and no linkage to the supporting bundle files that would make execution complete. This places it between anchors 3 and 4, short of mostly-executable guidance.

3 / 5

Workflow Clarity

The "Local evidence review" section presents a clearly sequenced 5-step process with explicit verification checkpoints ("Verify any source actually supplied", "Check whether the conclusion follows... which observation would change the conclusion"). It is not 5 because there is no feedback loop or checklist integration, and the existing evidence-boundary-checklist.md and review-rubric.md files that would supply them are never referenced.

4 / 5

Progressive Disclosure

The four bundle files in references/ (case-law.md, evidence-boundary-checklist.md, failure-taxonomy.md, review-rubric.md) are never referenced from the body, leaving ~25KB of directly relevant material undiscoverable, while the body points to paths that do not exist in the bundle (UPSTREAM.md, ../../../scripts/agent-rule-policy.json, ../code-review-excellence/SKILL.md). References are not merely unclear — they are absent, and the dead paths actively misdirect navigation, fitting anchor 2 rather than 3.

2 / 5

Total

12

/

20

Passed

Description

46%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 is (a reference-only CrossFrame archive with a local evidence-review fallback) and is distinctive thanks to the CrossFrame proper noun. However, it lacks any "Use when..." trigger guidance, leans on technical jargon rather than natural user phrases, and devotes much of its length to stating what is unavailable rather than what it concretely does.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to review evidence, verify claims against supplied sources, or assess whether conclusions follow from evidence."

Replace jargon-heavy framing ("source-fidelity certification", "upstream suite execution") with natural terms users would actually say, such as "review claims", "check sources", or "evidence review".

State 2-3 concrete actions the fallback performs (e.g. "separates facts from interpretations, verifies supplied sources, flags unsupported claims") instead of leading with what is unavailable.

DimensionReasoningScore

Specificity

"Reference-only CrossFrame archive" names the domain and "local evidence-review fallback" is one concrete capability, but the negative clauses ("suite execution and source-fidelity certification are unavailable") add no actions. It sits between anchor 2 and 4: only one concrete action is listed, which is more than pure domain-naming but short of several specific actions.

3 / 5

Completeness

The "what" is clearly stated (reference-only archive with a local evidence-review fallback), but there is no "Use when..." clause or any equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It is not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Only "evidence-review" and "archive" approach natural user phrasing; "CrossFrame", "source-fidelity certification", and "upstream suite execution" are technical jargon a user would not naturally say. Common natural phrases like "review these claims" or "check this evidence" are missing, so it does not reach anchor 3.

2 / 5

Distinctiveness Conflict Risk

The "CrossFrame" proper noun and the reference-only/archive framing carve a clear niche with minimal conflict risk against unrelated skills. It is not 5 because "evidence-review" overlaps with general review skills and the description offers no distinct trigger phrases to disambiguate.

4 / 5

Total

12

/

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.

Validation — 15 / 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

BigSimmo/Communication

Path

.agents/skills/crossframe-review/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.