PTENES
Skip to content
MODULE 2.2

🧰 Install the skill

Time to get hands-on. The storm-research are just two text files—there’s nothing to actually compile or install. You download them, drop them in the right folder, and confirm that Claude Code recognizes them. In three steps, you’re ready to run your first report.

6
Topics
~30
Minutes
Intermediate.
Level
Practical
Type
Module progress0%
0 of 6 topics read
1

⬇️ Download the files

The skill storm-research is made up of two text files: o SKILL.md (the 4-phase pipeline) and the report-template.html (the report template). Download both—there’s no installer, dependency, or paid service. Choose the language: PT-BR or EN use the same method; only the language of the internal prompts changes.

Install = download → drop into the folder → invoke 1 · download SKILL.md + template 2 · in the folder .claude/skills/storm-research/ 3 · invoke "run a storm research"

None of these steps is “installing” in the traditional sense: you download two text files (step 1), put them in the folder the agent scans (step 2), and call the skill in natural language (step 3). The following topics explain each step in detail.

⬇️ Download the skill and the template

The two files that make up the skill storm-research. In the next topic, you'll release them into .claude/skills/storm-research/ and the skill works — with no dependencies, scripts, or paid services.

Choose PT-BR or EN. You don't need to download both languages — one pair (SKILL.md + template) is enough.

📄 SKILL.md

The master prompt for the 4-phase STORM pipeline.

PT-BR ⬇️ EN ⬇️

🎨 report-template.html

The briefing’s HTML template—cloned, never recreated.

PT-BR ⬇️ EN ⬇️

💡 Tip — PT or EN?

Choose the language you feel comfortable reading: it affects the language of the five-lens prompts and the report titles. The method, phases, and verification are identical. If you'll share the briefing with an English-speaking audience, download the EN version.

A

Download the pair

SKILL.md + report-template.html, in the same language. By default, they go in your downloads folder.

B

Move to the skill folder

Both together in .claude/skills/storm-research/ (topic 2).

C

Confirm that it appears

Ask Claude Code to list the skills (topic 4). Ready to run.

2

📁 Where to put it

Both files live together in a folder named after the skill, inside ~/.claude/skills/. Claude Code scans this folder at startup and discovers the skill from its description from the frontmatter. One important detail: inside the folder, the instructions file must be called SKILL.md (without the suffix .pt/.en) and the template, report-template.html. The language suffixes are only there to help you tell them apart when downloading.

🎯 Objective: create the skill folder and move the two downloaded files into it, with their final names already in place (SKILL.md e report-template.html).

terminal · bashcopy and run
mkdir -p ~/.claude/skills/storm-research

mv <PASTA_DOWNLOADS>/storm-research.SKILL.<pt>.md \
   ~/.claude/skills/storm-research/SKILL.md

mv <PASTA_DOWNLOADS>/report-template.<pt>.html \
   ~/.claude/skills/storm-research/report-template.html

Replace the yellow sections: <PASTA_DOWNLOADS> from the folder where the browser saved it (e.g., ~/Downloads) e <pt> by pt or en, depending on the language you downloaded. The mv already renames them to their final names.

✅ How to verify: list the folder contents.

ls ~/.claude/skills/storm-research
# esperado:  SKILL.md   report-template.html

If both names appear, the skill is in the right place.

✓ Correct folder

  • ✓Both files TOGETHER in the same folder
  • ✓Folder named storm-research
  • ✓Instruction file called SKILL.md

✗ Where things tend to go wrong

  • ✗Files scattered across different folders
  • ✗Keep the name ...SKILL.pt.md
  • ✗Forget the report-template.html
3

🔀 Other agents

How the skill is text only + native tools, it’s portable: it runs in other command-line agents that follow the same skills convention. You don’t change anything in the files — only the root folder changes. The internal folder skills/storm-research/ and the two files remain identical.

Claude Code

~/.claude/skills/storm-research/

Codex

~/.codex/skills/storm-research/

Other agents

~/.agents/skills/storm-research/

🧳 Why this works

A storm-research doesn’t call any script, API, or paid service. It uses only what any compatible agent already provides: launching subagents, searching for and opening web pages, and writing files. That’s why the same pair of files is “installable” in any of them — just put them in the skills folder of the agent you use.

4

✅ Verify the installation

Before launching a real run, confirm that the agent can "see" the skill. The simplest way is to open Claude Code in the folder where you’re working and ask in natural language to list the available skills.

🎯 Objective: confirm that Claude Code recognizes the storm-research and read your frontmatter.

paste into Claude Codeprompt
Liste as skills disponíveis e confirme que "storm-research"
aparece. Mostre a descrição dela.

✅ How to verify: Claude responds by listing the skills and cites storm-research — generally repeating the description from the frontmatter (something like "run Storm Research / HTML brief with multiple perspectives"). If the skill no appears, review the folder and file names (topic 6) and restart the session.

💡 Tip

If you just moved the files while the session was already open, the agent may not have reread the skills folder. Close and reopen Claude Code so it can scan .claude/skills/ again.

5

🎯 Provide context

STORM aims at the hands-on section — the “actionable insight”—in the target reader that it identifies in Phase 0. If you don't say anything, it assumes "a professional or decision-maker in the field." But if you tell it who you are and what your business is, every report is tailored to your role instead of to a generic person.

example of a context linepaste before running
Sou <fundador de uma agência de automação em n8n>.
Quando rodar storm-research, mire o insight acionável
no meu papel: <o que eu preciso decidir>.

Replace the yellow sections with your real context. The more specific the role, the more useful the report’s actionable moves section becomes.

💡 Tip — persistent context

If you run STORM often, it’s worth recording this context in your CLAUDE.md for the project. That way, every report is tailored to your role from the start, without needing to repeat the context line each time you run it. (Deeper customization comes in Track 3.)

6

🧯 Common errors

Almost every “the skill doesn’t appear” or “it ran without the template” issue falls into one of these four categories. Check the right-hand column before asking for help.

✗ What tends to break

  • ✗Wrong folder—outside .claude/skills/
  • ✗Downloaded only the SKILL.md, without the template
  • ✗Kept the name ...SKILL.pt.md
  • ✗No read permission for the folder

✓ The right way

  • ✓Folder ~/.claude/skills/storm-research/
  • ✓Both files together in the folder
  • ✓Renamed to SKILL.md e report-template.html
  • ✓Reopened the agent after moving the files

Self-recovery (optional): where should the skill's two files go?

📌 Module summary

✓
The skill consists of two text files — SKILL.md + report-template.html, no installer.
✓
They live together in the skill folder — ~/.claude/skills/storm-research/, with the final names.
✓
The same skill is portable — only the root folder changes in Codex and other agents.
✓
Confirm before running — ask for the list of skills and provide context about your role.

Next module:

2.3 — The Pipeline in 4 Phases

← Back to Track Next Module →