Lead Magnets
sickn33/agentic-awesome-skills
Plan and optimize lead magnets for email capture and lead generation.
Write H2 chapter lead blocks (sections/S<secidlead.md) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts.
No licenceAuto-check passed
Install Chapter Lead Writer
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills chapter-lead-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/chapter-lead-writer .claude/skills/chapter-lead-writer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "chapter-lead-writer" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/chapter-lead-writer into .claude/skills/chapter-lead-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chapter-lead-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/chapter-lead-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills chapter-lead-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/chapter-lead-writer .agents/skills/chapter-lead-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chapter-lead-writer" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/chapter-lead-writer into .agents/skills/chapter-lead-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chapter-lead-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills chapter-lead-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/chapter-lead-writer .cursor/skills/chapter-lead-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chapter-lead-writer" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/chapter-lead-writer into .cursor/skills/chapter-lead-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chapter-lead-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/WILLOSCAR/research-units-pipeline-skills.git --path .codex/skills/chapter-lead-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills chapter-lead-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/chapter-lead-writer .gemini/skills/chapter-lead-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "chapter-lead-writer" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/chapter-lead-writer into .gemini/skills/chapter-lead-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chapter-lead-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install WILLOSCAR/research-units-pipeline-skills chapter-lead-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/chapter-lead-writer .github/skills/chapter-lead-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "chapter-lead-writer" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/chapter-lead-writer into .github/skills/chapter-lead-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chapter-lead-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills chapter-lead-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/chapter-lead-writer .opencode/skills/chapter-lead-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chapter-lead-writer" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/chapter-lead-writer into .opencode/skills/chapter-lead-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chapter-lead-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
chapter-lead-writer- GitHub stars
- 513
- Token cost
- ~1.5k tokens
- SKILL.md length
- 694 words
- Files
- 9 (incl. scripts, references, assets)
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- None found
At a glance
Write H2 chapter lead blocks (sections/S<secidlead.md) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts.
- SKILL.md covers Triggers & routing, Purpose, Migration status and Inputs, plus 10 more sections
- Runs Python scripts from its folder; calls uv
What it does
Chapter Lead Writer is an agent skill from WILLOSCAR/research-units-pipeline-skills. Write H2 chapter lead blocks (sections/S<secidlead.md) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts, reference files and assets (for example `assets/lead_block_compatibility_defaults.json`, `assets/lead_block_contract.json` and `references/bad_narration_examples.md`).
The repository describes itself as: Research pipelines as semantic execution units: each skill declares inputs/outputs, acceptance criteria, and guardrails. Evidence-first methodology prevents hollow writing…
Example prompts
- “/chapter-lead-writer”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit c92912a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Chapter Lead Writer loads about 1.5k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 45 tokens; SKILL.md has 694 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 694 words (~1,461 tokens).
“This skill writes the body-only lead block that sits under an H2 heading and makes a chapter with multiple H3 subsections read like one argument.”
- name
- chapter-lead-writer
Files
SKILL.md and 8 other files (scripts, references, assets) in .codex/skills/chapter-lead-writer of WILLOSCAR/research-units-pipeline-skills.
- SKILL.md
- assets/lead_block_compatibility_defaults.json
- assets/lead_block_contract.json
- references/bad_narration_examples.md
- references/bridge_examples.md
- references/lead_block_archetypes.md
- references/overview.md
- references/throughline_patterns.md
- scripts/run.py
Open the folder on GitHubat commit c92912a
Compare with similar skills
Chapter Lead Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chapter Lead Writer this skillWILLOSCAR/research-units-pipeline-skills | 513 | — | ~1.5k | Automated safety check: Pass | None | |
| Lead Magnetssickn33/agentic-awesome-skills | 47k | 2 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Block Kitopenclaw/openclaw | 392k | — | ~624 | Automated safety check: Pass | MIT | |
| Introduction Section Writeraipoch/medical-research-skills | 2k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Results Section Writeraipoch/medical-research-skills | 2k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Lead Magnetscoreyhaines31/marketingskills | 54k | 5 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
Block Kit
openclaw/openclaw
Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.
Introduction Section Writer
aipoch/medical-research-skills
Writes the full Introduction section of a biomedical manuscript based on an approved or sufficiently clear study logic, while preserving evidence boundaries and introduction discipline.
Results Section Writer
aipoch/medical-research-skills
Writes the full Results section of a biomedical manuscript from a sufficiently clear result structure, figure inventory, or analysis summary while preserving evidence boundaries and result hierarchy.
Lead Magnets
coreyhaines31/marketingskills
When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation.
Methods Section Writer
aipoch/medical-research-skills
Turns your protocol and analysis workflow into publication-ready Methods text.
More from WILLOSCAR/research-units-pipeline-skills
All 107 skills in this repoAppendix Table Writer
WILLOSCAR/research-units-pipeline-skills
Curate reader-facing survey tables for the Appendix (clean layout + high information density), using only in-scope evidence and existing citation keys.
Artifact Contract Auditor
WILLOSCAR/research-units-pipeline-skills
Audit one research Workspace for declared Unit outputs and Pipeline target Artifacts, writing output/CONTRACTREPORT.md; use for mid-Run coverage snapshots or final delivery completeness, not deep…
Arxiv Search
WILLOSCAR/research-units-pipeline-skills
Retrieve arXiv paper metadata with keyword queries or import an offline arXiv export, and save results as JSONL (papers/papersraw.jsonl).
Chapter Skeleton
WILLOSCAR/research-units-pipeline-skills
Build a retrieval-informed chapter skeleton (outline/chapterskeleton.yml) from taxonomy/core scope before stable H3 decomposition.
Dedupe Rank
WILLOSCAR/research-units-pipeline-skills
A skill your agent uses when a broad paper candidate pool needs deterministic deduplication and a stable core set.
Evaluation Anchor Checker
WILLOSCAR/research-units-pipeline-skills
Audit and rewrite evaluation/numeric claims to ensure they carry minimal protocol context (task + metric + constraint) and avoid underspecified model naming.
Questions about Chapter Lead Writer
What does Chapter Lead Writer do?
Write H2 chapter lead blocks (sections/S<secidlead.md) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts. Chapter Lead Writer is an agent skill from WILLOSCAR/research-units-pipeline-skills.md) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts.
How do I install Chapter Lead Writer in Claude Code?
Run `npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a claude-code`. Or copy the skill folder (.codex/skills/chapter-lead-writer in WILLOSCAR/research-units-pipeline-skills) into .claude/skills/chapter-lead-writer in your project. Claude Code loads it when a task matches its description.
How do I install Chapter Lead Writer in Codex?
Run `npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a codex`. Or copy the skill folder (.codex/skills/chapter-lead-writer in WILLOSCAR/research-units-pipeline-skills) into .agents/skills/chapter-lead-writer in your project. Codex loads it when a task matches its description.
Can I use Chapter Lead Writer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WILLOSCAR/research-units-pipeline-skills --skill chapter-lead-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chapter-lead-writer, .gemini/skills/chapter-lead-writer, .github/skills/chapter-lead-writer and .opencode/skills/chapter-lead-writer in your project.
What does Chapter Lead Writer need to run?
Going by SKILL.md and its folder, Chapter Lead Writer needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.
Does Chapter Lead Writer access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Chapter Lead Writer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Chapter Lead Writer use?
No licence was found for Chapter Lead Writer or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Chapter Lead Writer use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
What are the alternatives to Chapter Lead Writer?
Skills that share tags, products or a category with Chapter Lead Writer: Lead Magnets (sickn33/agentic-awesome-skills, 47k stars), Block Kit (openclaw/openclaw, 392k stars), Introduction Section Writer (aipoch/medical-research-skills, 2k stars) and Results Section Writer (aipoch/medical-research-skills, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chapter Lead Writer?
WILLOSCAR (a GitHub user) maintains it in WILLOSCAR/research-units-pipeline-skills, which has 513 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on October 5, 2026.
Source: WILLOSCAR/research-units-pipeline-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.