How to use the Obsidian Claude Gradient Deck agent skill

What does this skill make the agent do?

An agent skill is a folder containing instructions that an AI agent reads when a task matches the skill. This one is a style guide. Its SKILL.md describes a layout for a developer tutorial deck, modelled loosely on GitHub Blog and Linear Changelog pages, and the folder includes one example HTML file showing the look.

When the skill is active and you ask for a technical tutorial deck, the agent follows this layout instead of a generic one. The layout includes a GitHub-dark background (#0d1117), purple and blue radial ambient light over a 60px grid mask, centred content with a purple pill tag, headings with a three-colour gradient (#a855f7 to #60a5fa to #34d399), and a GitHub-style code palette with a purple left-border highlight block.

The skill does not do anything on its own. It does not run code, fetch data or export files. It only shapes how the agent designs the slides.

Install the skill from the ZIP download

Download the ZIP of the skill from this page. Unzip it and place the folder in one of two locations. For a personal skill available in all your projects, put it in ~/.claude/skills/. For a skill that only applies to one project, put it in that project's .claude/skills/ folder.

If you use the Claude apps instead, you can upload the skill under Settings → Capabilities → Skills rather than copying files by hand.

The folder should contain SKILL.md and example.html. Keep SKILL.md at the top level of the skill folder so the agent can find its instructions.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills (upload)

Trigger the skill with a natural request

You do not need a special command. Describe the deck you want and mention its purpose and style. The skill is tied to technical tutorial and changelog decks, so say that you want a developer-style or GitHub-like deck about a software topic.

Naming the look you want helps. Phrases such as 'dark developer tutorial deck' or 'changelog-style slides with code blocks' match what the skill is written for. If the agent uses a different style, ask it explicitly to follow the deck-obsidian-claude skill.

Examples of requests that work well

Clear, specific requests give the best results. Include the topic, the audience and roughly how many slides you want. Add any code samples you want shown.

• Make a 10-slide tutorial deck introducing our CLI tool, with code blocks for each install and usage step, in the dark GitHub style.
• Build a changelog deck for version 2 of our library, one slide per notable change, using the developer deck style.
• Prepare a 16:9 technical talk deck about how our build pipeline works, with a title slide, architecture diagram placeholders and code examples.

What does the skill need and what are its limits?

The skill lists no requirements. It does not run scripts and does not use the network. Its visual style is fixed to a dark developer theme, so it is a poor fit for corporate-branded decks or anything meant to be printed or shown on light backgrounds.

Because the template is a style guide rather than a tool, the output is an HTML-based design the agent produces following the example. Check the result in a browser before presenting.

• No listed requirements
• Runs scripts: no
• Uses network: no
• Dark theme only; no light version

Tips for better results

Keep each slide focused on one idea, since the layout suits short headings and code blocks. Ask for code examples to be placed in the styled code blocks. If you want the look without the purple accents, the skill itself is fixed, so you would need to edit SKILL.md yourself.

• Give the slide count and aspect ratio (the skill hints at 16:9).
• Mention that the deck is for developers so the agent keeps the technical tone.
• Review the example.html file to preview the style before you ask for a full deck.