CtrlK
BlogDocsLog inGet started
Tessl Logo

scientific-writing

This is the core skill for the deep research and writing tool—combining AI-driven deep research with well-formatted written outputs. Every document produced is backed by comprehensive literature search and verified citations through the research-lookup skill.

48

Quality

53%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/scientific-writing/SKILL.md

The canonical home for this skill is scientific-writing in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 skill delivers actionable, copy-paste-ready guidance and a well-sequenced manuscript workflow, but it is significantly over-long, explaining basic scientific-writing concepts Claude already knows and inlining material that should live in reference files. Progressive disclosure is undermined by both the inline bulk and the absence of the referenced bundle files.

Suggestions

Move the field-specific terminology section and the figure-requirement tables into dedicated reference files, keeping SKILL.md as a concise overview that links to them.

Cut explanations of concepts Claude already knows (common figure types, basic gene/chemical/species nomenclature, SI units) and retain only field-specific conventions that are non-obvious.

Reduce the redundant mandatory-figure emphasis (repeated MANDATORY/CRITICAL/EXTENSIVELY blocks) to a single concise instruction, and create the referenced references/, scripts/, and assets/ files so signaled paths resolve.

DimensionReasoningScore

Conciseness

The body is noticeably verbose and explains concepts Claude already knows — IMRAD definitions, common figure types ('Bar graphs: Comparing discrete categories'), and field nomenclature across seven subsections (gene italics, IUPAC, binomial nomenclature, SI units) — plus heavily padded redundant emphasis ('MANDATORY', 'CRITICAL', 'EXTENSIVELY') on figure generation. Not a 1 because the content is on-topic rather than off-domain padding, and not a 3 because the unnecessary explanations are extensive, not occasional.

2 / 5

Actionability

Provides mostly executable guidance: copy-paste bash commands ('python scripts/generate_schematic.py "..." -o figures/...'), full LaTeX environments, and a concrete two-stage outline-to-prose example with sample text. Not a 5 because some guidance stays abstract ('Establish the research problem's importance') and referenced scripts are not verified present, and not a 3 because the concrete code/commands substantially cover common cases.

4 / 5

Workflow Clarity

A clear four-stage manuscript workflow (Planning, Drafting, Revision, Final Preparation) plus a sequenced two-stage writing process, with the Revision stage acting as a checkpoint. Not a 5 because explicit validate→fix→retry feedback loops are absent, and not a 3 because the sequence is well-defined with checkpoints; the destructive/batch validation cap does not apply to a writing skill.

4 / 5

Progressive Disclosure

References are signaled one level deep ('refer to references/imrad_structure.md'), but large sections that belong in reference files are inlined (the seven-subsection field terminology guide, figure-requirement tables, LaTeX examples), and no references/, scripts/, or assets/ bundle directories exist so the signaled paths lead nowhere. Not a 4 because content that should be separate is substantially inline and the bundle is missing, and not a 2 because section headers and reference signals do provide some structure.

3 / 5

Total

13

/

20

Passed

Description

50%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 conveys what the skill does at a high level but omits any explicit 'when to use' trigger guidance, capping its completeness. It is adequately specific and reasonably distinct but lacks the concrete trigger phrases and synonyms that would make it reliably surfaceable.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when writing or revising a scientific manuscript, structuring a research paper (IMRAD), formatting citations, or preparing a journal submission.'

Include natural user synonyms and file/format terms ('manuscript', 'paper', 'article', 'journal submission', 'abstract', 'PRISMA/CONSORT/STROBE') to broaden trigger coverage.

List more specific concrete actions (e.g. 'draft IMRAD sections', 'format APA/AMA/Vancouver citations', 'apply CONSORT/STROBE/PRISMA checklists') to raise specificity from abstract to comprehensive.

DimensionReasoningScore

Specificity

Names the domain (deep research + writing) and a couple of concrete actions ('well-formatted written outputs', 'literature search', 'verified citations'), but stays abstract ('core skill for the deep research and writing tool') and is not comprehensive. Not a 4 because it does not list several specific actions, and not a 2 because it does name real capabilities beyond the domain.

3 / 5

Completeness

It clearly answers 'what' the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric. Not a 4 because 'when' is entirely absent rather than weakly implied.

3 / 5

Trigger Term Quality

Relevant terms like 'deep research', 'writing', 'literature search', and 'citations' appear, but common user synonyms ('manuscript', 'paper', 'article', 'journal submission') are missing. Not a 4 because natural variations are sparse, and not a 2 because the terms present are more than one or two generic keywords.

3 / 5

Distinctiveness Conflict Risk

The 'deep research and writing' niche is somewhat specific and ties itself to the research-lookup skill, but the framing is broad enough to overlap with other research/writing skills. Not a 4 because the triggers are not sharply distinct, and not a 2 because it is more specific than generic 'helps with documents'.

3 / 5

Total

12

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (720 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 22 missing

Warning

Total

12

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.