nature-shared

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

Quality

60%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is exceptionally concise and sequences its single load-and-defer workflow clearly, but its actionability is held back by abstract directory references rather than named files, and progressive disclosure suffers because the referenced core/ and journal-formats/ paths are not present in the bundle.

Suggestions

Name at least one concrete example file (e.g., an actual core or journal-format filename) so the load directive is copy-paste-ready.

Either add the missing `core/` and `journal-formats/` directories with their files, or remove/qualify those references so the body points only to bundle paths that exist.

Dimension	Reasoning	Score
Conciseness	The 8-line body is lean and assumes Claude's competence: a purpose statement plus three crisp rules with no concept exposition or padding, matching the score-3 anchor.	3 / 3
Actionability	It gives concrete directives ("Load the exact referenced file; do not preload the whole package," "Return to the requesting skill for task logic, output format, and final QA") but never names an actual file, leaving the referenced core/journal-format paths abstract and short of copy-paste-ready concreteness.	2 / 3
Workflow Clarity	As a simple single-purpose skill it lays out an unambiguous sequence (use only as a dependency -> load the exact requested file -> treat dirs as shared definitions -> return to the requesting skill for logic and QA), satisfying the simple-skills latitude for a 3.	3 / 3
Progressive Disclosure	The body is well-organized for a short skill, but it references `core/` and `journal-formats/` directories that do not exist in the bundle (no references/, scripts/, or assets/ present), so the signaled navigation does not resolve to real files.	2 / 3
	Total	10 / 12 Passed

Description

42%

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 is clear about its limited support-package role and strongly disambiguates itself from standalone skills, but it lacks natural trigger terms and a positive "Use when" clause. It is written in correct third-person voice with no over-claims.

Suggestions

Add a brief positive trigger clause (e.g., 'Use only when another Nature skill requests a core or journal-format definition file') to raise completeness and trigger coverage.

Include a couple of natural user-facing terms a requesting skill or user might reference (e.g., 'nature-writing', 'journal-format definitions') to improve trigger term quality beyond internal jargon.

Dimension	Reasoning	Score
Specificity	It names the domain ("Internal shared-reference support package" for four named Nature skills) and a concrete action ("Load only the specific core or journal-format file requested by another Nature skill"), but does not list multiple specific user-facing actions, so it sits at the score-2 anchor rather than 3.	2 / 3
Completeness	It clearly answers "what" (a shared-reference support package that loads specific files) and gives a constrained request-driven "when," but it lacks a positive "Use when..." trigger clause, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	It contains no natural user-facing trigger terms; "Nature skill", "core", and "journal-format file" are internal jargon, and it explicitly states "Do not invoke it as a standalone user workflow," so there are no keywords a user would naturally say.	1 / 3
Distinctiveness Conflict Risk	It names four sibling skills and explicitly disambiguates ("Do not invoke it as a standalone user workflow," "Load only... requested by another Nature skill"), carving a clear niche with very low conflict risk.	3 / 3
	Total	8 / 12 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: 703c150

Reviewed: 4 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.