AI4S Skills
Seven skills for planning research, reviewing literature, preparing experiment code and drafting a paper with traceable sources
- 266 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent executes generated experiment code, and the installer replaces matching skill folders
- The agent opens external pages to confirm every bibliographic reference
- It creates PDF, LaTeX and result files in the project's output directory
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/ai4s-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent executes generated experiment code, and the installer replaces matching skill folders
- The agent opens external pages to confirm every bibliographic reference
- It creates PDF, LaTeX and result files in the project's output directory
This is third-party code. Review the repository files before installing.
What it does
AI4S Skills gives an agent a workflow for computational research. It first compares directions and prepares a preliminary review, then builds a literature survey with a bibliography. For the chosen topic, the experiment skill outlines the design, writes runnable code and records results with the provenance of each number. The writing skill assembles those materials into a paper draft. Stages share a topic identifier and output directories, so work can resume from an existing survey or use your own data. When the topic is already fixed, the initial exploration stage is skipped. A separate skill checks another paper for inconsistencies in images, numbers and reasoning. It ranks findings by strength of evidence; a specialist must assess the conclusions. Another tool renders a topic map from the matrix prepared by the agent.
Who it is for. For researchers, graduate students and engineers who prepare a survey or paper with Claude Code, Cursor or Codex and want to see the source of every citation and number.
Good fit when
- You have only a field, for example neural operators for partial differential equations, and need to pick a concrete topic with a literature pre-survey
- You need a PDF literature survey with LaTeX sources and a bibliography.bib reference list
- You need a runnable experiment so that the paper's numbers have their provenance recorded in results.json
- You want to check someone else's paper by DOI or arXiv for duplicated images and numbers that do not add up
- You want to go from a direction to a paper in one request through ai4s-agent
Not a fit when
- You want to publish without review: every document needs a domain expert, as the skills themselves state
- You need a short answer to one question: the full pipeline produces PDFs of dozens of pages
- You do humanities or field research: the example and tools in the repository target computational experiments
- You plan to use the auditor's output as an accusation: it reports a confidence grade and no verdict
Example request
Use the literature-survey skill and write a survey on neural operators for the Burgers equation, with the sources as BibTeXLimitations
A finished PDF remains a draft for specialist review. Without real results, the experiment stage may use plausible simulated numbers; tables and captions must disclose this. The presence of runnable code does not prove the experiment was executed.
The installer needs Bash and replaces existing skill folders with matching names, so back up local edits first. Charts and helper tools need Python and their dependencies; PDF output requires LaTeX. The agent opens external sources, executes code and handles documents through the chosen model. The collection uses MIT.
How to disable. Remove the relevant folders from the project’s .claude/skills directory or global ~/.claude/skills directory. Generated material remains under output and can be removed separately.
FAQ
How do I install AI4S Skills in Claude Code?
From the target project directory, run install.sh using its absolute path in the clone. The installation section shows both paths. Run `/path/to/ai4s-skills/install.sh paper-writer` with your clone path to install only the writing stage; omit the argument to install all skills.
How do the skills hand work to each other?
Through a shared topic slug and the path output/<skill>/<slug>/latest/. Every skill computes the slug from the topic string the same way, so paper-writer finds the survey and experiment results without manual pointers.
How do the skills verify the bibliography?
The instructions require opening each cited work’s page during the current session and taking bibliographic details from it. This is a rule for the agent; authors still need to check citations and source relevance before submission.
What does integrity-auditor check?
The review covers images, numerical results and reasoning. Tools can look for repeated image regions and inconsistencies across tables. Findings are presented with a strength of evidence; a person must assess any claim of misconduct.
Which agents does AI4S Skills work with?
The author names Claude Code, Cursor, Codex and Aider. Claude Code reads skills from .claude/skills, and for the others you give the path to the needed SKILL.md in the request.
Discussion
No questions or reviews yet.
Related
SkillsAI Vibe Writing Skills
AI-Vibe-Writing-Skills
Skill pack for academic papers covering author voice, evidence-based arguments, sentence flow and formal replies to reviewers.
Claude Code skills for the academic pipeline: research, paper drafting, peer review and citation checks
Research Skills
research-skills
Skills for scientific work: literature reviews on AI in medical imaging, a manuscript audit, slides. No paywall bypass, data comes from OpenAlex and PubMed
paper-reading-skill turns one arXiv AI or robotics paper into a report with each claim tied to evidence in the source.
A marketplace of five Claude Code plugins for researchers: literature search, research design, project memory and manuscript work
A skill that checks a manuscript against practices of 883 ICLR, ICML and NeurIPS Oral papers and suggests edits
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| AI4S Skills (this card) | no | 266 | |
| AI Research Skills | no | 14,317 | a skill library for ML research from idea to paper; AI4S stresses traceable citations and numbers |
| Academic Research Skills | no | 55,620 | research, paper writing, peer review and citation checks step by step |
README in short
The survey, experiment and paper-writing instructions can be used without the overall orchestrator. Long tasks save intermediate material to files so work can continue in a later session.
README badge
Original SKILL.md
---
name: ai4s-agent
description: Use when the user wants an end-to-end AI4S research pipeline — broad direction or specific topic in, full research package out (exploration + literature survey + experiment + paper). Meta-skill that chains the four downstream skills in order. Pure markdown, no Python runtime.
---
# AI4S Agent (meta-skill)
## Overview
Top-level entry point for the AI4S research stack. This skill contains **no work of its own** — its only job is to call four downstream skills in the right order, with the right slug, and reuse intermediate artifacts by path convention.
```
direction → research-explorer → topic
topic → literature-survey (60+ real bib, 100+ recommended)
topic → experiment-suite (design + code + results + figures)
topic → paper-writer (assembles into 200+ cite PDF)
```
Each downstream skill is **already single-stage and self-sufficient**: its agent loads that skill's `SKILL.md` and produces the full final-quality artifact directly. There is no skeleton/enrichment split. This meta-skill only handles ordering, the path convention, and disclosure consistency.
## When to use
- User asks for "a paper on X" or "research package on X" and wants the whole stack run end to end.
- User wants to compare what each skill produces — useful for developing or debugging the pipeline itself.
## When NOT to use
- User wants to run only one stage (e.g. only the literature survey) → invoke that skill directly.
- User wants only topic exploration → invoke `research-explorer` directly.
## The slug contract
Every skill computes the same slug from the same topic string:
```python
import re, hashlib
def slug(t):
n = re.sub(r'[\s_]+', '-', re.sub(r'[^\w\s-]', '', t.lower().strip())).strip('-')[:40].rstrip('-')
h = hashlib.sha1(t.encode()).hexdigest()[:8]
return f"{n}-{h}"
```
Use the **same string** across all four skills. If the user provides a direction (not a topic), `research-explorer` runs against the direction; once a topic is chosen, the topic becomes the slug input for the remaining three.
## Workflow
### Step 1 — Understand the user's starting point
- **Direction** ("transformer time series forecasting") — start at `research-explorer`, pick a topic from its `research_exploration.md`, then proceed.
- **Topic** ("Transformer-based long-horizon forecasting with patch tokenisation") — skip `research-explorer`; go straight to the parallel branch (literature-survey, experiment-suite, paper-writer).