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

82%

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

70%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, validation-rich derivation workflow with strong sequencing and a concrete file template, but the single-file monolithic structure (no supporting reference files) and noticeable length/repetition pull down progressive disclosure and conciseness.

Suggestions

Split the long Required File Structure template and Output Modes detail into a reference file (e.g., references/DERIVATION_TEMPLATE.md) referenced one level deep from SKILL.md to improve progressive disclosure.

Trim repeated guidance: the invariant-object and assumption/notation rules are restated across Steps 3-4, Step 8, and Key Rules; consolidate to reduce token cost.

Add one short worked derivation example (target -> invariant object -> labeled steps) so the guidance is copy-paste ready and fully actionable.

Dimension	Reasoning	Score
Conciseness	The 285-line body is mostly efficient and assumes Claude's competence (no boilerplate concept explanations), but it is notably long with repeated restatements (e.g., invariant-object and assumption guidance appears in Steps 3-4 and again in Key Rules), so it sits at 'mostly efficient but could be tightened' rather than the leaner 4.	3 / 5
Actionability	Provides concrete, executable guidance: an explicit required file structure template, status constants, file-resolution priority, and concrete classification categories (identity/proposition/approximation/interpretation); minor gaps are that there is no worked example of an actual derivation step, so it is not fully copy-paste ready at 5.	4 / 5
Workflow Clarity	Eight clearly sequenced steps with explicit verification in Step 8, a final verification checklist, a feedback loop ('If the derivation still lacks a coherent object... downgrade the status and write a blocker report'), and explicit validation before writing; this matches the clear-sequence-with-validation-and-feedback anchor.	5 / 5
Progressive Disclosure	No bundle files (references/scripts/assets) are present and the body is essentially a monolithic single-file document with no one-level-deep references to separate files; internal section structure exists but nothing is split out, matching 'some structure but could be better organized' rather than the well-split 5.	3 / 5
	Total	15 / 20 Passed

Description

95%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, third-person description with concrete actions, explicit 'Use when' triggers, and clear boundary language separating it from theorem-proof skills. Minor specificity gaps (e.g., no mention of explicit output formats like blocker reports) keep it just below a perfect specificity score.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('structures and derives research formulas', 'build a theory line', 'organize assumptions', 'turn scattered equations into a coherent derivation', 'rewrite theory notes into a paper-ready formula document') with only minor gaps in coverage, fitting the 'several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Clearly answers 'what' (structures/derives research formulas, builds theory lines, organizes assumptions, rewrites notes) and 'when' via the explicit 'Use when...' clause with concrete trigger conditions ('derivation target is not yet fully fixed', 'main object still needs to be chosen', 'needs a coherent derivation package rather than a finished theorem proof').	5 / 5
Trigger Term Quality	Comprehensive natural-language coverage including the bilingual trigger '推导公式' plus user phrasings like 'build a theory line', 'organize assumptions', 'rewrite theory notes into a paper-ready formula document', and 'coherent derivation package' matching the breadth of the 5 anchor.	5 / 5
Distinctiveness Conflict Risk	The skill occupies a clear niche (derivation/theory-line construction) and explicitly distinguishes its scope from proof-writing ('rather than a finished theorem proof'), minimizing conflict risk with adjacent skills.	5 / 5
	Total	19 / 20 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: 4b35756

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