aris-formula-derivation

Structures and derives research formulas when the user wants to 推导公式, build a theory line, organize assumptions, turn scattered equations into a coherent derivation, or rewrite theory notes into a paper-ready formula document. Use when the derivation target is not yet fully fixed, the main object still needs to be chosen, or the user needs a coherent derivation package rather than a finished theorem proof.

Quality

88%

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

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 a well-sequenced, actionable methodology with a strong verification feedback loop and a ready-to-fill document template, but it is verbose with some repetition between the workflow and Key Rules, and it makes no use of progressive disclosure despite its length.

Suggestions

Collapse the 'Key Rules' section into the relevant workflow steps (or vice versa) to remove the duplicated guidance about hiding gaps and separating identity/proposition/approximation/interpretation steps.

Extract the DERIVATION_PACKAGE.md file-structure template and the three 'Output Modes' into a referenced template file (e.g. references/derivation_template.md) so SKILL.md stays a lean overview and progressive disclosure improves.

Trim the repeated 'Do not...' prohibitions across Steps 5–7 and Key Rules to a single consolidated rules list to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient procedural guidance without padding Claude already knows, but the ~200-line document repeats guidance between the workflow steps and the 'Key Rules' section (e.g. 'do not hide gaps', 'separate assumptions/propositions/approximations'), so it could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready guidance for an instruction-only skill: a full DERIVATION_PACKAGE.md markdown template, exact STATUS enum values, and a fixed identity/proposition/approximation/interpretation step taxonomy to apply.	3 / 3
Workflow Clarity	Steps 1–8 are clearly sequenced and Step 8 (Final Verification) plus the 'If the derivation still lacks a coherent object... write a blocker report instead of forcing a clean story' rule form an explicit validation/feedback checkpoint.	3 / 3
Progressive Disclosure	The skill is well-sectioned but is a monolithic single file with no external references or split content; at over 50 lines it exceeds the simple-skill threshold that would let well-organized sections alone earn a 3.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 third-person, concise, and explicitly covers both capability and trigger conditions with concrete actions and natural trigger terms (including the user's native Chinese phrasing). It is clearly distinguished from the companion proof-writing skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Structures and derives research formulas', 'build a theory line', 'organize assumptions', 'turn scattered equations into a coherent derivation', and 'rewrite theory notes into a paper-ready formula document' — matching the score-3 anchor of several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Structures and derives research formulas...') and when via a clear 'Use when the derivation target is not yet fully fixed, the main object still needs to be chosen, or the user needs a coherent derivation package rather than a finished theorem proof' clause.	3 / 3
Trigger Term Quality	Captures natural phrasings a user would actually say, including the colloquial Chinese trigger '推导公式' alongside 'build a theory line' and 'rewrite theory notes into a paper-ready formula document', giving good coverage of likely user language.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — derivation/theory-line construction — and the 'rather than a finished theorem proof' framing plus the in-body contrast with aris-proof-writer make conflict with sibling skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: OpenLAIR/dr-claw
Path: skills/aris-formula-derivation/SKILL.md
Commit: 6da7f7c

Reviewed: about 7 hours 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.