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.

32

Quality

30%

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/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

35%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill suffers primarily from extreme verbosity—it reads like a textbook on scientific writing rather than a concise instruction set for Claude. It explains numerous concepts Claude already knows (what bar graphs are for, what active voice means, basic writing principles) and includes encyclopedic sections on field-specific terminology that add little actionable value. The strongest sections are the outline-to-prose conversion example and the LaTeX formatting guidance, but these are buried in hundreds of lines of general writing advice.

Suggestions

Cut the content by 60-70%: Remove sections explaining concepts Claude already knows (basic writing principles, what different chart types are for, field-specific terminology conventions). Focus only on project-specific tools, workflows, and conventions that Claude wouldn't know.

Move the field-specific terminology section (Section 10), detailed figure type descriptions, and writing principles entirely to reference files—these are exactly the kind of content that should be progressively disclosed rather than inlined.

Add explicit validation checkpoints to the manuscript workflow: e.g., 'Run reporting guideline checklist before proceeding to Stage 3' with a concrete command or checklist reference, and 'If checklist reveals gaps, return to the relevant section in Stage 2.'

Consolidate the visual enhancement section: the minimum figure requirements table and extensive lists of when to use each tool could be reduced to a brief rule ('Generate figures liberally using scientific-schematics for technical diagrams and generate-image for visual content') with a reference to detailed guidance.

DimensionReasoningScore

Conciseness

This skill is extremely verbose at ~600+ lines, extensively explaining concepts Claude already knows (what IMRAD is, what active voice means, what a scatterplot is, basic writing advice like 'eliminate redundant words'). Entire sections like field-specific terminology (biomedical, chemistry, ecology, physics, neuroscience) are encyclopedic padding that Claude inherently understands. The document explains basic concepts like 'bar graphs: comparing discrete categories' and 'use precise, unambiguous language.'

1 / 5

Actionability

The skill provides some concrete guidance (LaTeX code examples for scientific_report.sty, bash commands for figure generation, example outline-to-prose conversion), but much of the content is descriptive rather than instructive. Many sections are abstract guidance ('establish research context, identify gaps, state objectives') rather than executable steps. The writing process example with the outline-to-prose conversion is genuinely useful and concrete, but it's buried in hundreds of lines of vague advice.

3 / 5

Workflow Clarity

The manuscript development workflow (Stages 1-4) provides a reasonable sequence, but validation checkpoints are mostly implicit ('check logical flow,' 'verify consistency') rather than explicit with concrete verification steps. There are no feedback loops for error recovery—for example, no step says 'if reporting guideline checklist reveals gaps, return to Stage 2 to address them.' The two-stage writing process (outline → prose) is clearly sequenced but lacks validation.

3 / 5

Progressive Disclosure

The skill references multiple external files (references/imrad_structure.md, references/citation_styles.md, etc.) and assets, which is good progressive disclosure in principle. However, no bundle files were provided to verify these exist, and the SKILL.md itself inlines enormous amounts of content that should be in those reference files (e.g., the entire field-specific terminology section, detailed LaTeX examples, figure generation guidance). The references section at the end properly signals external files, but the body doesn't actually defer to them—it duplicates and expands on the content.

3 / 5

Total

10

/

20

Passed

Description

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

This description reads like a marketing overview rather than a functional skill description. It lacks concrete actions, natural trigger terms, and explicit 'when to use' guidance. The vague language ('AI-driven deep research', 'well-formatted written outputs') makes it difficult for Claude to distinguish this skill from other research or writing skills in a large skill library.

Suggestions

Add a 'Use when...' clause with specific trigger phrases, e.g., 'Use when the user asks for a research report, literature review, academic paper, or any document requiring sourced citations.'

Replace vague language with concrete actions, e.g., 'Searches academic databases, synthesizes findings from multiple sources, generates structured reports with inline citations and bibliographies.'

Include natural user terms and synonyms such as 'research paper', 'literature review', 'find sources', 'write a report', 'cited document' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('deep research and writing') but actions are vague—'combining AI-driven deep research with well-formatted written outputs' doesn't specify concrete actions like 'searches databases', 'synthesizes findings', or 'generates reports'. The phrase 'comprehensive literature search and verified citations' adds slight specificity but remains abstract.

2 / 5

Completeness

The 'what' is vaguely described as combining research with written outputs, but there is no explicit 'when' clause or trigger guidance. The description reads more like a marketing blurb than actionable selection criteria. The absence of a 'Use when...' clause caps this at 3, and the vague 'what' brings it down to 2.

2 / 5

Trigger Term Quality

Contains some relevant terms like 'deep research', 'writing', 'literature search', and 'citations', but these are fairly generic. Missing natural user phrases like 'write a report', 'research paper', 'find sources', 'literature review', 'academic writing', or specific output formats.

2 / 5

Distinctiveness Conflict Risk

The description is very broad—'research and writing tool' could overlap with many skills involving writing, research, summarization, or document generation. The mention of 'research-lookup skill' dependency adds some context but doesn't sufficiently narrow the niche. Terms like 'well-formatted written outputs' are generic enough to conflict with many other skills.

2 / 5

Total

8

/

20

Passed

Validation

72%

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

Validation8 / 11 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

Total

8

/

11

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.