nature-shared

Internal shared-reference support package for installed Nature Skills, including nature-writing, nature-polishing, nature-response, nature-reader, and nature-paper2ppt. Do not invoke it as a standalone user workflow. Load only the specific core or journal-format file requested by another Nature skill.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nature-shared/SKILL.md

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.

The body is a lean, well-structured index that routes each purpose to a specific shared file and delimits scope per file — the right shape for a dependency package. However, the entire routing table is dangling: none of the referenced core/ or journal-formats/ files exist in the bundle, and the one file that does exist (scripts/check_consistency.py) is never mentioned. Tightening the repeated caveats and making the references resolve would lift it substantially.

Suggestions

Ship or restore the referenced core/ and journal-formats/ files so every entry in the routing table resolves; as listed, all referenced paths are dangling.

Reference scripts/check_consistency.py (e.g., as a pre-return consistency check) so the only bundled script is discoverable from SKILL.md.

Factor the repeated 'do not present it as official journal policy' and do-not-import caveats into a single shared rule line, and add a fallback step for when a requested file is absent from the bundle.

Dimension	Reasoning	Score
Conciseness	The body is an efficient routing table with no explanations of concepts Claude already knows, matching 'efficient; minor instances that could be trimmed'. Not a 5 because the caveat 'do not present it as official journal policy' is repeated in four bullets and the do-not-import pattern recurs, which could be factored into a single line.	4 / 5
Actionability	Routing is concrete at the file level ('Use `core/nature-abstract.md` for corpus-derived Nature-style discovery-centred abstract compression'), but the key detail is missing: no core/ or journal-formats/ files exist in the actual bundle, so the load instructions cannot be executed as written. Not a 4 because dangling targets are a substantive gap, not a minor one.	3 / 5
Workflow Clarity	The dependency lifecycle is clear and single-purpose: 'Load the exact referenced file; do not preload the whole package', apply the per-file scope limits, then 'Return to the requesting skill for task logic, output format, and final QA' — a clean sequence with defined boundaries. Not a 5 because there is no checkpoint for unresolvable requests, which matters given none of the referenced files are present.	4 / 5
Progressive Disclosure	The body is a well-annotated one-level index (each entry names a file and its scope), but scored against the actual bundle structure every referenced path under core/ and journal-formats/ is missing, while the one bundled file, scripts/check_consistency.py, is never referenced. The organization intent is good but the reference structure does not resolve.	3 / 5
	Total	14 / 20 Passed

Description

66%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 clear, honest self-description for an internal dependency package: it states what it is, when it applies (only when requested by another Nature skill), and which skills it serves. Its main weaknesses are that it contains only one concrete action verb and its keywords are internal routing terms rather than natural user phrasing, leaving discovery and trigger coverage thinner than its scope delimitation.

Suggestions

Add an affirmative trigger clause (e.g., 'Load when an installed Nature skill requests a core/ or journal-formats/ file') so the when-condition reads as an explicit trigger rather than only a prohibition.

Include natural search terms for the covered domains (e.g., Nature journal formatting, abstracts, Introductions, Results/Discussion style) so the package is discoverable beyond its internal skill names.

State where the core/ and journal-formats/ files live so the file-loading promise in the description is verifiable against the bundle.

Dimension	Reasoning	Score
Specificity	The description names its domain ("Internal shared-reference support package for installed Nature Skills") and one concrete action ("Load only the specific core or journal-format file requested by another Nature skill"), matching the anchor for a domain plus 1-2 concrete actions. It is not a 4 because 'load' is the only real action verb; the rest is scope delimitation and a list of dependent skills rather than a set of capabilities.	3 / 5
Completeness	Both parts are explicit: the 'what' ("shared-reference support package ... Load only the specific core or journal-format file") and the 'when' ("Do not invoke it as a standalone user workflow ... requested by another Nature skill"). Not a 5 because the trigger is expressed only as a prohibition plus a dependency condition, with no affirmative concrete trigger phrase; it clears a 3 since both what and when are explicitly stated.	4 / 5
Trigger Term Quality	Relevant keywords are present ("Nature Skills", "nature-writing, nature-polishing, nature-response, nature-reader, and nature-paper2ppt", "core", "journal-format") but these are internal routing vocabulary with no natural user-facing phrases or synonyms. Not a 4 because common natural variations a user would actually say are absent, though the five named skills keep it above a 2.	3 / 5
Distinctiveness Conflict Risk	The explicit non-invocation directive ("Do not invoke it as a standalone user workflow") plus the enumerated dependent skills give it a clear niche with minimal conflict risk — no other skill would be wrongly triggered by this description.	5 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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: Yuan1z0825/nature-skills
Path: skills/nature-shared/SKILL.md
Commit: 50851ef

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.