CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

check-cross-layer

Post-implementation verification across multiple code dimensions: cross-layer data flow, code reuse analysis, import path validation, and same-layer consistency checks. Identifies missed update sites, type mismatches, and duplicated constants. Use when changes span 3+ architectural layers, after modifying shared constants or configs, after batch file modifications, or when creating new utility functions.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/check-cross-layer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-structured with actionable commands and checklists, but suffers from redundancy (B2/B3 duplicating B, a restated quick-reference table), a missing fix-and-re-verify feedback loop for a batch-modification skill, and detailed-guide references that point to files not shipped in the bundle.

Suggestions

Add an explicit feedback loop: after applying fixes for found issues, re-run the grep checks (e.g. `grep -r "patternYouChanged" src/`) to confirm no remaining occurrences before reporting done.

Merge Dimensions B2 and B3 into Dimension B and remove or trim the Common Issues Quick Reference table, which restates checklist content — this would tighten the skill considerably.

Resolve the dangling `.trellis/spec/guides/*.md` references: either ship the guides in a `references/` directory with skill-relative paths, or remove the "Detailed Guide" pointers so navigation never dead-ends.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete tables and checklists, but includes tightening opportunities: the motivational opener ("Most bugs come from 'didn't think of it', not lack of technical skill"), the Common Issues Quick Reference table restating checklist content, and Dimensions B2/B3 largely duplicating Dimension B's items. This is more than the "minor instances" of anchor 4, so anchor 3 fits best.

3 / 5

Actionability

Provides executable commands ("git status", "git diff --name-only", "grep -r \"value-to-change\" src/"), a layer-location table with real directory names, and itemized checklists. The grep commands are placeholder templates requiring substitution, so guidance is mostly executable with minor gaps (anchor 4) rather than fully copy-paste ready (anchor 5).

4 / 5

Workflow Clarity

A clear sequence exists (identify scope, select dimensions, run checklists, report output) and the checklists act as checkpoints, but there is no fix-and-re-verify feedback loop — the workflow ends at "Issues found and fix suggestions". Because the skill is explicitly triggered after batch file modifications, the rubric's batch-operation cap limits workflow_clarity to 3.

3 / 5

Progressive Disclosure

Section structure is clear with per-dimension headers and clearly signaled "Detailed Guide" pointers, but all referenced guides (e.g. ".trellis/spec/guides/cross-layer-thinking-guide.md") are absent from the skill bundle, leaving the reference layer dangling. Structure could be better organized (bundle the guides or remove the pointers), matching anchor 3 rather than the minor-gaps anchor at 4.

3 / 5

Total

13

/

20

Passed

Description

88%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 strong description: it names concrete capabilities in third person and pairs them with an explicit multi-condition "Use when" clause. Trigger coverage is good though not exhaustive of natural synonyms, and there is minor overlap risk with general code-review skills.

DimensionReasoningScore

Specificity

Lists four concrete verification dimensions ("cross-layer data flow, code reuse analysis, import path validation, and same-layer consistency checks") plus concrete outputs ("missed update sites, type mismatches, and duplicated constants") in third-person voice, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Clearly answers both questions: the "what" is explicit (post-implementation verification across four named dimensions) and the "when" is an explicit "Use when..." clause with four concrete trigger conditions, exactly matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

The "Use when" clause covers several natural trigger phrases ("changes span 3+ architectural layers", "after modifying shared constants or configs", "after batch file modifications", "creating new utility functions"), but common variations like "refactor", "duplicate code", or "missed updates" are absent, matching anchor 4 rather than the synonym-level coverage of 5.

4 / 5

Distinctiveness Conflict Risk

"Post-implementation verification" establishes a distinct niche, but triggers like "changes span 3+ architectural layers" and "code reuse analysis" overlap with general code-review skills, matching anchor 4 (mostly distinct, minor overlap risk) rather than the minimal-conflict anchor at 5.

4 / 5

Total

18

/

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

relative_links

Relative link issues: 3 missing, 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

202780181/lingxiData

Path

.agents/skills/check-cross-layer/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.