How to use the Enterprise AI Adoption Brief Deck agent skill

What does this skill make the agent do?

An agent skill is a folder of instructions and files that an AI agent loads when your request matches it. This skill turns a topic about rolling out AI inside a company into a presentation-ready HTML slide deck in a dark purple gradient look, based on the obsidian-claude-gradient template.

The agent first asks for missing essentials such as audience, decision goal and key numbers. It then drafts a slide plan, slide text, visual direction, speaker notes, and a self-review against a funding-readiness checklist. The output is a web page you open in a browser, not a PowerPoint or PDF file.

• Asks for missing inputs: audience, decision target, source-of-truth materials, deadline and must-keep numbers
• Produces a slide plan, written slides and visual direction
• Adds speaker notes that are kept out of the visible slides
• Runs a critic pass against a funding-readiness rubric

What do you need before installing?

This skill is a pointer to a larger master skill called html-ppt, and it depends on that skill's template and asset folders. Both must be present in the same place, or the deck will not work. You also need a web browser to view the HTML output. The skill does not run scripts and does not use the network.

• The parent html-ppt master skill, including its template and asset folders at design-templates/html-ppt/
• A web browser to view the HTML file
• The item's files: example.html and SKILL.md

How do you install the skill?

Download the ZIP from the skill's page on this site and unzip it. To make it available across all your projects, place the folder in your personal skills directory. To limit it to one project, place it in that project's .claude/skills/ folder instead.

If you use the Claude apps rather than a local setup, you can upload the skill instead. Open Settings, go to Capabilities, then Skills, and upload the skill there. Make sure the html-ppt master skill and its template folders are installed as well.

• Personal install: unzip into ~/.claude/skills/
• Project install: unzip into the project's .claude/skills/ folder
• Claude apps: Settings → Capabilities → Skills, then upload

How do you trigger the skill with a natural request?

You do not need a special command. Describe what you want in plain words that match the skill's topic and keywords, such as the rollout of AI in a company, a decision brief for leadership, or an HTML deck. The skill's example prompt is a good starting point, and you can adapt it to your topic.

Give the agent your subject and audience up front. If you leave out the audience, decision target, source materials, deadline or must-keep numbers, the agent should ask for them before drafting. Answering these questions is what makes the deck specific enough to be useful.

• Example: Create an enterprise AI adoption brief as an HTML deck for leadership, IT and security, with a decision to approve a pilot.
• Example: Draft a rollout plan deck in the obsidian-claude-gradient template for our transformation committee.
• Example: Write speaker notes and a slide plan for an AI adoption brief, and critique it against a funding checklist.

What should you provide so the deck is accurate?

The skill provides structure, wording and visual style. It does not supply facts. If you want numbers such as return on investment or security claims in the deck, supply the source data yourself. Without source data, the agent cannot verify figures, and invented numbers would be risky in a funding decision.

Keep speaker notes out of visible slide text. The skill places them inside an aside or div with the class notes, so they stay hidden on the slide.

• Give the agent your source documents and must-keep numbers
• Check every figure and claim against your own records before presenting
• Review speaker notes separately from the slides

How do you make the HTML deck work in a project?

Copy index.html and style.css from the obsidian-claude-gradient template folder into your project, and keep the template's body class. The template's index.html loads shared CSS and JavaScript using parent-relative paths, which break once the file leaves its original folder. Choose one of two fixes per project.

Recipe A copies the shared files into a project-local assets folder and rewrites the four link and script tags to point there. Recipe B inlines the contents of those four files into the HTML so you get a single self-contained file. Do not ship the original ../../../assets/ paths in a project, because they only work inside the original folder tree.

• Recipe A (preferred): copy fonts.css, base.css, animations/animations.css and runtime.js into a local assets folder and update the tags
• Recipe B: replace the link and script tags with style and script blocks containing the same files
• Optional: swap in one of the 36 themes from the themes folder by changing the theme link