Skip to main content
Agent skill

Codex Interactive Capability Map

Turn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Codex Interactive Capability Map when an AI agent needs a reusable SKILL.md workflow for this job: Turn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.

When not to use it

Skip Codex Interactive Capability Map when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/codex-interactive-capability-map
# Save SKILL.md to ~/.claude/skills/codex-interactive-capability-map/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/codex-interactive-capability-map/SKILL.md. For a shared project, commit the folder at .claude/skills/codex-interactive-capability-map/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Codex Interactive Capability Map skill for this task: Read the source material and extract 6-10 core concepts. Confirm any required inputs or files before making changes.

What supports this recommendation?

75/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
76/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Codex Interactive Capability Map

Transform a long article, social thread, memo, product essay, or launch narrative into a visual explainer that people can scan and click through.

## Use When

- The input is mostly text and the user wants a clearer mental model. - The content contains repeated concepts, a process, a framework, capabilities, or operating principles. - The desired output is a polished web artifact, not a static summary.

## Workflow

1. Read the source material and extract 6-10 core concepts. 2. Name the overall model in plain language. Prefer a short noun phrase such as "Operating Model", "Capability Map", or "Workflow Loop". 3. Build three linked views: - A hero that frames the source and the promise. - A workflow loop that shows the main sequence or system. - A use-case matrix that combines concepts into practical scenarios. 4. Add a right-side detail panel. Clicking any nav item, loop node, matrix card, or maturity level must update the panel. 5. Make the clicked element and the detail panel visibly correspond through shared color, motion, icon/mark shape, or gradient. 6. Keep copy short. The artifact should reduce reading effort, not recreate the article.

## Visual Direction

- Use a Codex-inspired refined product style with soft liquid motion, glassy surfaces, and crisp functional controls. - Make the first viewport feel like a finished product surface, not a wireframe. - Favor diagrams, loops, matrices, rails, cards, and progressive disclosure over paragraphs. - Use meaningful hover and active states. A click should feel consequential. - Avoid external image dependencies unless the user explicitly provides assets.

## Interaction Requirements

- All clickable elements must update content or scroll to a meaningful section. - The active state must be visually obvious. - The detail panel should animate on each change. - Long labels must wrap cleanly and never be clipped. - The layout must work at 1280px wide and collapse cleanly below 900px.

## Output Contract

Emit one single-file HTML artifact:

```html <artifact identifier="codex-interactive-capability-map" type="text/html" title="Codex Interactive Capability Map"> <!doctype html> <html>...</html> </artifact> ```

Include all CSS and JavaScript inline. Do not use lorem ipsum. Do not leave placeholder cards. If the source does not include enough concrete details, infer a small, clearly labeled conceptual model from the source instead of inventing unrelated content.

Intended uses

  • Read the source material and extract 6-10 core concepts.
  • Name the overall model in plain language. Prefer a short noun phrase such as "Operating Model", "Capability Map", or "Workflow Loop".
  • Build three linked views:
  • A hero that frames the source and the promise.
  • A workflow loop that shows the main sequence or system.
  • A use-case matrix that combines concepts into practical scenarios.
  • Add a right-side detail panel. Clicking any nav item, loop node, matrix card, or maturity level must update the panel.
  • Make the clicked element and the detail panel visibly correspond through shared color, motion, icon/mark shape, or gradient.
  • Keep copy short. The artifact should reduce reading effort, not recreate the article.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.