CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

comm-lit-review

Communications-domain literature review with Claude-style knowledge-base-first retrieval. Use when the task is about communications, wireless, networking, satellite/NTN, Wi-Fi, cellular, transport protocols, congestion control, routing, scheduling, MAC/PHY, rate adaptation, channel estimation, beamforming, or communication-system research and the user wants papers, related work, a survey, or a landscape summary.

63

Quality

79%

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/comm-lit-review/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.

A well-structured, navigable instruction skill with concrete search policy, a defined deliverable table, and graceful degradation rules. Its main costs are systematic repetition of the source/venue ladder across four sections and the absence of any progressive disclosure — the venue catalog and fact-extraction fields are inlined in a 290-line file rather than split into reference files.

Suggestions

State the source list and database ladder once (e.g., in Source Selection) and have Retrieval Order, External Search Policy, Step 1, and Key Rules reference it, cutting roughly 60-80 lines of repetition.

Move the Tier A/B/C venue catalog into a references/ file (e.g. references/venues.md) linked from a short 'Venue Priority' section, keeping SKILL.md as an overview.

Add a verification checkpoint after Step 2, e.g. 'If fewer than N relevant papers are found in a tier, widen to the next tier and re-search' to make the sparse-result loop explicit.

DimensionReasoningScore

Conciseness

The body is mostly efficient bullet-style policy, but the source ladder is repeated four times — 'zotero, obsidian, local, ieee, sciencedirect, acm, web' appears in Source Selection defaults, Valid source values, Retrieval Order, and the Output source list, and the database ladder recurs in Retrieval Order, External Search Policy, Step 1, and Key Rules. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not a 4 because the redundancy is systematic rather than a few minor trims.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact glob paths ('papers/**/*.pdf and literature/**/*.pdf'), a defined output table with ten named columns, a fixed five-part summary order, and explicit source-parsing syntax ('$ARGUMENTS for a — sources: directive'). It stays at 4 rather than 5 because there are no copy-ready command/query templates (e.g., example Zotero MCP searches or WebSearch phrasings) for the common cases.

4 / 5

Workflow Clarity

Steps are clearly sequenced (Step 0a/0b/0c → 1 → 2 → Synthesis → Output) with explicit skip conditions ('Skip this step if Zotero MCP is not configured') and degradation checkpoints ('If a source is unavailable, do not fail. Skip it silently.'). Not a 5 because there are no verification/feedback checkpoints — e.g., nothing instructs re-checking that found papers actually match the topic or re-searching when a tier comes up sparse — which are stated only as implicit 'widen if sparse' rules.

4 / 5

Progressive Disclosure

This is a single ~290-line SKILL.md with no references/, scripts/, or assets/ bundle at all. Sections are well-organized and flat (one level, easy to navigate), but content that plausibly belongs in a separate reference — the ~50-line Tier A/B/C venue catalog and the field-listing for paper facts — is fully inlined, matching anchor 3 ('content that should be separate is inline'). It is above 2 because structure and headers are good and nothing is buried.

3 / 5

Total

14

/

20

Passed

Description

86%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 with explicit 'what' and 'when' structure and comprehensive, natural domain trigger terms. Its main weakness is that the capability side is thin — 'knowledge-base-first retrieval' is abstract — and the generic survey/papers triggers create minor overlap with general literature-review skills.

Suggestions

Replace or expand 'Claude-style knowledge-base-first retrieval' with concrete actions, e.g. 'searches the user's Zotero/Obsidian libraries and local PDFs first, then IEEE/ScienceDirect/ACM, and synthesizes a landscape table'.

Qualify the generic triggers ('papers, related work, a survey') so they only fire for communications topics, e.g. 'when the topic is a communications/networking question and the user wants papers...'.

State the deliverable explicitly (e.g. 'produces a grouped literature table with venue, year, and relevance') to strengthen the 'what' side.

DimensionReasoningScore

Specificity

The description names the domain and two actions — 'Communications-domain literature review' and 'knowledge-base-first retrieval' — but 'Claude-style knowledge-base-first retrieval' is abstract and no other concrete actions (survey generation, paper extraction, table synthesis) are stated. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; a 4 would require several specific actions listed, and the extensive keyword list enumerates topics, not capabilities.

3 / 5

Completeness

Both parts are explicit: 'what' is stated ('Communications-domain literature review with Claude-style knowledge-base-first retrieval') and 'when' is stated with concrete triggers ('Use when the task is about ... and the user wants papers, related work, a survey, or a landscape summary'). This mirrors the 5-anchor exemplar structure of action statement plus 'Use when...' clause; a 4 would have a weaker or less specific 'when'.

5 / 5

Trigger Term Quality

Natural trigger coverage is comprehensive: 'communications, wireless, networking, satellite/NTN, Wi-Fi, cellular, transport protocols, congestion control, routing, scheduling, MAC/PHY, rate adaptation, channel estimation, beamforming' plus task-phrase synonyms 'papers, related work, a survey, or a landscape summary'. These are exactly the words a user would say, with both lay terms (Wi-Fi, cellular) and technical synonyms (MAC/PHY, ACM-free jargon kept natural). Not below 5 since no common variation or synonym is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — communications-specific terms like 'satellite/NTN', 'beamforming', 'MAC/PHY', 'channel estimation' are unlikely to fire a generic skill. However the closing triggers 'papers, related work, a survey' overlap with any general literature-review skill, giving minor overlap risk with closely related skills — matching anchor 4 ('Mostly distinct; minor overlap risk') rather than 5's 'minimal conflict risk'.

4 / 5

Total

17

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/comm-lit-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.