Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Abstract And Title

ASecurity

Write and sharpen research paper titles, abstracts (structured and unstructured), keywords, highlights, significance statements, graphical-abstract text and lay summaries. Use when drafting or revising an abstract to a word limit, turning results into a one-sentence contribution, choosing between candidate titles, writing Cell/Elsevier highlights, a PNAS significance statement or a plain-language summary, or optimizing discoverability (keywords, search terms).

7 stars
0 votes
0 copies
2 views
Added 10/4/2026
researchgo

Works with

cli

Security Analysis

A100/100

Scanned 10/4/2026

$npx -y skills add KalarisLabs/research-agent-skills --skill abstract-and-title --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Abstract And Title?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Abstract And Title
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kalarislabs-abstract-and-title/badge)](https://www.skillsdirectory.com/skills/kalarislabs-abstract-and-title)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: abstract-and-title
description: Write and sharpen research paper titles, abstracts (structured and unstructured), keywords, highlights, significance statements, graphical-abstract text and lay summaries. Use when drafting or revising an abstract to a word limit, turning results into a one-sentence contribution, choosing between candidate titles, writing Cell/Elsevier highlights, a PNAS significance statement or a plain-language summary, or optimizing discoverability (keywords, search terms).
license: MIT
compatibility: No runtime dependencies.
metadata:
  version: "1.0"
  category: research-writing
  maintainer: Kalaris Labs
  author: Kalaris Labs (Sayan Chowdhury)
  tags: abstract, title, keywords, highlights, significance statement, lay summary, scientific writing
---

# Titles, Abstracts and Summary Text

Most readers, editors and reviewers decide from the title and abstract alone.
They are also what search engines and indexing services see. Write them last,
from the finished results, and revise them more than any other part of the paper.

## Inputs to collect first

- The single main finding, with its key number (effect size, accuracy, p-value/CI, sample size).
- The target venue's limits: abstract word count, structured vs. unstructured, title length,
  keyword count, highlights/significance requirements. **Look these up in the venue's current
  author guidelines** (the `venue-templates` skill and journal-format skills help). Never assume.
- Who reads it: specialists (field venue) or broad scientists (Nature, Science, PNAS).

## Abstract: the five-move structure

Unstructured abstracts still follow these moves. Structured ones label them.

| Move | Share | Content |
|---|---|---|
| Context | 1 sentence | The broader problem, in terms the venue's readers care about |
| Gap | 1 sentence | What is unknown, unsolved or wrong. Make the gap concrete |
| Approach | 1-2 sentences | What you did: design, data, method, with the essential scale (n, datasets) |
| Results | 2-3 sentences | The main findings **with numbers**. Lead with the most important |
| Implication | 1 sentence | What changes because of this, bounded by what the evidence supports |

Structured formats: IMRaD (Background/Methods/Results/Conclusions) for most clinical
journals. CONSORT-for-abstracts for RCTs. PRISMA 2020 for Abstracts for systematic reviews.
Some journals (e.g. BMJ) use their own headings, so match the journal exactly.

**Rules:**
- Numbers beat adjectives: "reduced error by 23% (95% CI 18-28%)" not "substantially reduced error".
- No citations, undefined abbreviations, or claims not in the paper. Define an abbreviation only if used ≥2 times.
- Past tense for what you did and found; present tense for established facts and implications.
- Keep it self-contained: a reader should understand it without the paper.
- Hit the limit without padding. If over, cut context before results.

## Titles

Generate 5-10 candidates across types, then pick against the criteria:

- **Declarative** (states the finding): "Metformin reduces hepatic glucose output via complex IV inhibition".
  Common in biology/medicine and broad journals.
- **Descriptive** (states the topic/method): "A graph neural network for retrosynthesis planning".
  Common in CS/engineering.
- **Question**: use sparingly, only when the answer is genuinely surprising.

Criteria: accurate (no overclaiming), specific (organism, method, population), contains
the 2-3 terms people search for, within the venue's length limit, no abbreviations
except universal ones (DNA, MRI), no puns that hide the content. Check that no existing
paper already has a near-identical title.

## Keywords

Choose terms **not already in the title** to widen discoverability: synonyms, the broader
field, method names, organism/population. Prefer controlled vocabulary where the venue
uses it (MeSH for biomedicine, ACM CCS concepts, IEEE Taxonomy, JEL codes, PACS/PhySH).

## Venue-specific extras

| Element | Typical form (verify per venue) |
|---|---|
| Highlights (Cell Press, Elsevier) | 3-5 bullets, each up to ~85 characters including spaces, results-focused |
| eTOC blurb / In Brief (Cell Press) | Short third-person paragraph for non-specialists |
| Significance statement (PNAS) | Plain-language paragraph on why the work matters to a broad audience |
| Author summary (PLOS) | Non-technical summary for a general reader |
| Lay / plain-language summary | Health and life-science journals, funders: no jargon, ~reading age 12-14 |
| Graphical abstract | One image read left-to-right or top-to-bottom: problem → approach → key result |
| Teaser / tweet-length | One sentence with the key number, for press and social media |

## Revision checklist

1. Does the first sentence establish why this matters to *this venue's* readers?
2. Is the gap stated explicitly, not implied?
3. Does every result sentence contain a number or concrete outcome?
4. Is every claim supported in the main text, at the same strength?
5. Word count within the limit (count it, don't estimate)?
6. Would a researcher from an adjacent field understand it?
7. Do title, abstract, highlights and conclusions tell the *same* story with the same numbers?

## Related skills

`scientific-writing`, `ml-paper-writing`, `cover-letter-to-editor`, `venue-templates`,
journal-format skills (`nature-portfolio`, `cell-press`, `plos`, ...), `scientific-slides`.

Attribution

KalarisLabsKalarisLabs
View sourceSee grades on GitHubMore from KalarisLabs →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Competitor Analysis

This skill provides comprehensive analysis of competitor SEO and GEO strategies, revealing what's working in your market and identifying opportunities to outperform the competition.

1823 votes

Deep Research

Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 8 modes: full research, quick brief, paper review, lit-review, fact-check, three-way literature scan, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report co...

502942 votes

Paperclip Distill

Use when an operation issue is a Paperclip cursor-window, distill, or backfill — `operationType: "distill"` or `"backfill"` and the body references a Paperclip source bundle for a project or root issue. Turn raw Paperclip activity into a wiki-insightful project page, decisions log, and history note. This skill exists specifically to replace the stiff, datestamp-heavy templated output that the deterministic distiller produces.

953191 votes

Academic Pipeline

Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory, coverage-bounded integrity checks, two-stage peer review, and auditable quality-assurance artifacts. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end p...

502941 votes

Literature Review

Assistance with writing literature reviews by searching for academic sources via Semantic Scholar, OpenAlex, Crossref and PubMed APIs. Use when the user needs to find papers on a topic, get details for specific DOIs, or draft sections of a literature review with proper citations.

6511 votes
View all in research →