AF authorship-credit-gen
Use when determining author order on research manuscripts, assigning CRediT contributor roles for transparency, documenting individual contributions to collaborative projects, or resolving authorship disputes in multi-institutional research. Generates fair and transparent authorship assignments following ICMJE guidelines and CRediT taxonomy. Helps research teams document contributions, resolve disputes, and ensure equitable credit distribution in academic publications.
As a process F 65/100 · Will not run — References files that are not bundled: references/guide.md, references/examples/, references/api-docs/
The same skill appears in 1 more place: ClawHub
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/guide.md - warning
missing-refreference to a missing file: references/examples/ - warning
missing-refreference to a missing file: references/api-docs/ - note
frontmatter-keyunknown frontmatter key "skill-author"
Process rating: all ten parameters 65/100
- 0Tools and files. 3 referenced file(s) missing: references/guide.md, references/examples/, references/api-docs/
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (authorship-credit-gen) differs from the folder (authorship-credit-gen-1)
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 63 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 2778 tokens
- 100Progress reporting. Reports progress
- low 20 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +3Description length 473: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 63 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.