Twitter/X

On 2026-05-10, @alex_prompter instructs Claude Code users to run "use…

2026-05-10 · 11:37 UTC ·@alex_prompter ·1 min read

Brief

The post by @alex_prompter (2026-05-10) tells Claude Code users to invoke "use /skill-creator" and build skills with a /references folder, /assets folder, and a main SKILL markdown router. It requires a pre-generation compatibility check, surfacing restructuring issues and asking clarifying questions, and to explicitly list any non-text assets needed rather than creating placeholders.

Why it matters

On 2026-05-10, @alex_prompter instructs Claude Code users to run "use /skill-creator" and create a skill that includes a /references folder for framework docs, an /assets folder for templates/swipe files, and a main SKILL markdown file that acts as the router pointing to them.

Key details

  • Before generating the multi-file skill, the assistant must evaluate the mega-prompt for compatibility: if the prompt is too short, too narrow, or lacks structured knowledge, recommend keeping it as a standalone prompt or expanding it, and surface any parts that would require heavy restructuring and ask clarifying questions.
  • @alex_prompter mandates explicitly flagging any reference or asset files that cannot be created from text alone (images, audio, video), listing exactly which assets are missing and what each should contain, refusing to generate placeholder or fake content; warns that a single 10,000-word SKILL markdown will 'choke' and recommends splitting into reference files.
Source evidence

Open Claude Code and type:

"use /skill-creator and create [skill-name] using the following information:

[PASTE PROMPT HERE]

When you turn this into a skill make sure it has a /references folder for framework docs, an /assets folder for templates and swipe files, and the main SKILL markdown as the router that points to them. Split the prompt's knowledge into the appropriate reference files.

Before generating the skill, evaluate the mega-prompt for compatibility. If the prompt is too short, too narrow, or doesn't have enough structured knowledge to justify a multi-file skill, tell me directly and recommend either keeping it as a standalone prompt or expanding it first. If parts of the prompt would require heavy restructuring to fit the skill format, surface those concerns and ask clarifying questions before proceeding.

Also flag any reference or asset files that cannot be created from text alone. If a swipe file folder would need images, screenshots, audio samples, video references, or other non-text assets, do not generate placeholder files or fake content. Instead, list exactly which assets are missing, describe what each one should contain, and ask me to provide them before finalizing the skill."

One SKILL markdown trying to hold 10,000 words of instructions will choke. Splitting it into reference files keeps each piece focused and lets the model pull only what it needs per task.