At a glance
Status, checked 2026-09-18: the skill is part of the electricblaze repository and npm package 0.1.2. It covers Instagram only and says so: TikTok and YouTube are marked planned, and real posts are routed to the widget until the 0.2 API.
- Use it when
- you or your team build sites with a coding agent and want Instagram feed requests handled the same way every time, with the account step handed to a human.
- Do not use it when
- the project already has its own Instagram integration that works. The skill would suggest replacing a fetch you are happy with.
- What the human does
- approves the install. Later, the site owner connects the Instagram account when real posts are needed.
- Next step
- run
npx electricblaze skillin the project, ornpx skills add ElectricBlaze/electricblazefor any agent the skills CLI supports.
Install it
| You use | Command | Installs to |
|---|---|---|
| Claude Code and Codex, per project | npx electricblaze skill | .claude/skills/ and .agents/skills/; --agent=claude or --agent=codex picks one |
| Any agent the skills CLI knows | npx skills add ElectricBlaze/electricblaze | The directory of the agent you choose; -a claude-code -y skips the questions |
| Claude Code, as a plugin | /plugin marketplace add ElectricBlaze/electricblaze, then /plugin install electricblaze@electricblaze | Your Claude Code plugins |
| By hand | Copy skills/electricblaze-feeds/ from the repository | Anywhere your agent reads skills |
We ran both command-line routes on 2026-09-18. npx skills add ElectricBlaze/electricblaze --list finds one skill, electricblaze-feeds. The electricblaze route prints what it wrote:
npx electricblaze skill --json in an empty project (paths trimmed)
{
"ok": true,
"skill": "electricblaze-feeds",
"agents": ["claude", "codex"],
"files": [
{ "agent": "claude", "path": ".claude/skills/electricblaze-feeds/SKILL.md", "status": "written" },
{ "agent": "claude", "path": ".claude/skills/electricblaze-feeds/references/schema.md", "status": "written" },
{ "agent": "claude", "path": ".claude/skills/electricblaze-feeds/references/platforms.md", "status": "written" },
{ "agent": "codex", "path": ".agents/skills/electricblaze-feeds/SKILL.md", "status": "written" },
{ "agent": "codex", "path": ".agents/skills/electricblaze-feeds/references/schema.md", "status": "written" },
{ "agent": "codex", "path": ".agents/skills/electricblaze-feeds/references/platforms.md", "status": "written" }
],
"next": "Start a new agent session in this project; the skill triggers on requests like \"add an Instagram feed to the footer\"."
}A skill you edited is never overwritten. Start a new agent session afterwards: agents read skill descriptions when a session begins.
When it triggers
An agent loads a skill when the request matches its description. This is the description, word for word:
Add an Instagram feed (posts, reels, carousels) to a website or app with ElectricBlaze; TikTok and YouTube feeds are planned, not available yet. Use when asked to show social media posts on a page, an Instagram grid or reels in a footer, or when Instagram Graph API / Basic Display API / access token questions come up.
Prompts that trigger it in practice: "show our latest Instagram posts in the footer", "add a reels strip to the home page", "my Instagram feed stopped working after Basic Display was shut down".
What it tells the agent to do
- Run
npx electricblaze add instagram-feed --jsonand readframework,files,notesandnext. - Wire the result in: the Server Component in Next.js, the four-line snippet in plain HTML, or a native component over the JSON for Astro, SvelteKit, Nuxt and the other
dataframeworks. - Restyle freely, but keep the "demo feed" label until real data flows.
- Filter on request:
formats={["reel"]}in Next.js,data-formats="reel"in HTML,limitfor fewer posts. - Check with
npx electricblaze doctor --json; every failing check carries anextcommand. - Hand the account step to a human: the widget today,
connectin 0.2.
The skill also carries a list of things never to do. It forbids scraping instagram.com, putting a token in a client-side fetch to graph.instagram.com, setting ELECTRICBLAZE_API_KEY before 0.2, editing feed.d.ts, and faking real posts by editing the demo JSON.
What is inside
| File | Contents |
|---|---|
SKILL.md | Front matter with name and description, the six-step workflow, the never-do list, a quick view of the data shape |
references/schema.md | Schema v1 field by field; the same contract as the schema page |
references/platforms.md | Instagram API facts with a check date and sources: Basic Display shutdown, professional accounts only, 60-day tokens, reel and carousel fields |
The format is the open Agent Skills standard: a folder with a SKILL.md that has YAML front matter. Claude Code reads it from .claude/skills/, Codex from .agents/skills/.
Without the skill: the AGENTS.md block
If a project has AGENTS.md or CLAUDE.md, npx electricblaze add appends a short block between <!-- electricblaze:start --> and <!-- electricblaze:end -->. It gives any agent that opens the project the essentials, even without the skill:
AGENTS.md (block written by add)
## Social feeds (ElectricBlaze)
The Instagram feed on this site comes from ElectricBlaze (TikTok and YouTube
are planned, not available yet). The feed shape is schema v1 (see the copied
`feed.d.ts`) ...
- `npx electricblaze preview instagram --json` prints the current feed
(demo data until an account is connected).
- `npx electricblaze doctor --json` checks the setup and explains what to do next.
- Real posts need a human. Today the site owner connects the account in the
ElectricBlaze widget at https://electricblaze.com and pastes its embed
snippet where the feed belongs. The JSON API for this component
(`npx electricblaze connect instagram`) ships in 0.2.Why a skill and not only docs
Without guidance a coding agent writes the Instagram code itself. The code looks right in review and fails weeks later. The usual failures are a long-lived token that expires after 60 days (Meta: access_token reference, checked 2026-09-18) and image links that stop loading on a cached page (media URL expired).
A skill moves the decision to the start of the task. The agent learns what exists today, what the human has to do, and which command gives it a working grid in one step.