CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 auth...

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/authorship-credit-gen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

31%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 reads as a plausible skills document but fails on execution and navigation: every Python example uses classes absent from scripts/main.py, three of four referenced files do not exist, and roughly a third of the content is duplicated or generic boilerplate. The workflow and error-handling sections are coherent but their validation steps would not catch any of these defects.

Suggestions

Fix the code examples to match the actual bundle: use the 'CRediTGenerator' class defined in scripts/main.py (or the argparse CLI via 'python scripts/main.py'), and remove the two conflicting import styles in Quick Start.

Delete the duplicated sections — 'When to Use' vs 'When to Use This Skill', the two 'References' blocks, and the overlapping 'Error Handling'/'Failure Handling' — and trim the generic 'Quality Checklist'/'Response Template' boilerplate to what is domain-specific.

Repair or remove the broken references to references/guide.md, references/examples/, and references/api-docs/, keeping only real bundle files such as references/audit-reference.md.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded or duplicated sections: two separate 'When to Use' sections repeating the same trigger text verbatim, two 'References' sections, overlapping 'Error Handling' and 'Failure Handling' sections, and generic boilerplate ('Quality Checklist', 'Response Template', 'Output Requirements') that adds no domain knowledge. Not a 1 because it does not explain concepts Claude already knows (no CRediT/ICMJE tutorials); not a 3 because the duplication is repeated across multiple sections, not just occasional slack.

2 / 5

Actionability

The code examples look concrete but are broken against the actual bundle: 'from scripts.main import AuthorshipCreditGen' and 'AuthorshipCreditGenerator(guidelines="ICMJEv4")' reference classes that do not exist — scripts/main.py defines 'CRediTGenerator', so the Quick Start and all Core Capabilities examples fail immediately with ImportError. Not a 1 because concrete commands and complete-looking code blocks are provided (the CLI usage 'python scripts/main.py --help' does work); not a 3 because the gap is not a missing detail — the primary API surface shown is wrong.

2 / 5

Workflow Clarity

The five-step 'Workflow' section is sequenced and includes validation (step 2) and a fallback path (step 5), plus a 'Quick Check' compile command. However, validation is superficial — 'py_compile' only checks syntax and would never catch the broken class references — and the duplicated error/failure sections fragment the guidance. Not a 4 because checkpoints do not actually verify the documented execution path; not a 2 because a coherent sequence with explicit fallback is present.

3 / 5

Progressive Disclosure

The body references 'references/guide.md', 'references/examples/', and 'references/api-docs/' — none of which exist in the bundle (only references/audit-reference.md exists), so navigation to the claimed detail is broken. Substantial boilerplate that belongs in separate files is inlined. Not a 1 because the body has clear section headers and one valid, one-level-deep reference; not a 3 because most advertised references are broken, which is worse than merely unclear signaling.

2 / 5

Total

9

/

20

Passed

Description

78%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.

The description is strong: explicit 'Use when' triggers, natural domain keywords, and a clearly distinct niche. Its main defect is that the capability ('what') sentence is truncated mid-word ('Generates fair and transparent auth...'), capping specificity and completeness just below the top anchor. Third-person voice is used correctly ('Generates', 'Helps').

Suggestions

Complete the truncated capability sentence (e.g., '...Generates fair and transparent authorship assignments following ICMJE guidelines and the CRediT taxonomy') so the 'what' is fully stated.

Add common natural variations users would say, such as 'author contribution statement', 'equal contributions', or 'who should be an author', to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'determining author order on research manuscripts', 'assigning CRediT contributor roles for transparency', 'documenting individual contributions to collaborative projects', 'resolving authorship disputes in multi-institutional research' — but the capability sentence is cut off mid-word ('Generates fair and transparent auth...'), leaving a minor gap in coverage. Not a 5 because the primary 'what' clause is truncated; not a 3 because the domain and four concrete actions are explicitly stated.

4 / 5

Completeness

Both what and when are present: an explicit 'Use when...' clause with concrete trigger conditions, plus a capability statement ('Generates fair and transparent auth...'). Not a 5 because the 'what' portion is truncated mid-word in the frontmatter; not a 3 because both elements are present and the 'when' is fully explicit with concrete triggers.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'author order', 'CRediT', 'contributor roles', 'authorship disputes', 'research manuscripts'. A few natural phrases users would say are missing (e.g., 'author contribution statement', 'who should be an author', 'equal contributions'). Not a 5 because synonyms and common variations are absent; not a 3 because coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche — research authorship, CRediT taxonomy, ICMJE guidelines, multi-institutional disputes — with distinct trigger phrases unlikely to collide with other skills. Matches the 'clear niche with distinct triggers; minimal conflict risk' anchor exactly.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/authorship-credit-gen/SKILL.md

Reviewed

Table of Contents

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.