HTMLHero.Skill logo

HTMLHero.Skill

Community
YiShu5
HTMLHero.skill

Build or extend a runnable, responsive Hero first screen for an HTML/React site or web presentation when the user provides a Hero brief, visual reference, media, or existing frontend. Use this for the Hero itself; use HTMLPPT.skill for a multi-slide deck.

Overview

PublisherYiShu5
Repositoryclaude-skills
Skill nameHTMLHero.skill
Stars
131
Forks
0
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by YiShu5 on GitHub. Read the source before you install it.

Installation

Install the HTMLHero.Skill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/YiShu5/claude-skills/tree/master/skills/HTMLHero.skill
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/YiShu5/claude-skills.git /tmp/claude-skills
mkdir -p .claude/skills
cp -r /tmp/claude-skills/skills/HTMLHero.skill .claude/skills/HTMLHero.skill
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable HTMLHero.Skill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads HTMLHero.Skill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so HTMLHero.Skill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

HTMLHero.skill

Turn a Hero brief or an existing first-screen implementation into a runnable, reviewable Hero. The first screen should establish a visual system that can be extended later.

Route

  • Use for a new or changed Hero first screen with layout, copy, media, or interaction.
  • If the request is a multi-slide HTML presentation, use HTMLPPT.skill instead.
  • If the request is only visual ideation or copy, do not force an implementation workflow.

Workflow

  1. Establish the finish line and scope. Inspect the target directory, recent AGENTS.md, package.json, lockfile, relevant entrypoints, and referenced assets. Do not read the whole repository by default.
  2. Resolve the smallest useful Hero contract: purpose and audience, required copy, visual references, media, interactions, target viewport, existing stack, and delivery target. Read references/hero-contract.md when inputs are incomplete or the work will be handed off.
  3. Apply constraints in this order: user request, existing design system and project conventions, then skill defaults. Make reversible assumptions and state them. Ask only when a missing decision materially changes the result or crosses a real permission boundary; a routine local implementation does not need a ritual confirmation.
  4. Implement in the existing stack and file structure. For a new project, choose the smallest viable starter for the requested output; do not force React, Tailwind, animation libraries, or new dependencies. Preserve unrelated dirty work and avoid overwriting files outside scope.
  5. Make the Hero usable without unavailable assets: provide a poster, gradient, local fallback, or explicit placeholder when appropriate. Keep CTA targets meaningful, use semantic HTML, and treat animation as optional and reduced-motion aware.
  6. Read references/validation.md for the relevant checks. Continue through build, preview, visual inspection, and fixes until the finish line is met or a concrete blocker remains.

Completion and delivery

A task is complete when the requested Hero is implemented, the available build/preview path has been exercised, the target viewport has been inspected, and material failures have been fixed or clearly reported. Do not stop after the first implementation merely to request review when the remaining work is safe and in scope.

Report the changed files, actual run/build commands and results, preview URL or entrypoint, visual/interaction checks, assumptions or fallbacks, and any concrete blocker. Only create a zip or publish when requested.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the HTMLHero.Skill AI skill do?

Build or extend a runnable, responsive Hero first screen for an HTML/React site or web presentation when the user provides a Hero brief, visual reference, media, or existing frontend. Use this for the Hero itself; use HTMLPPT.skill for a multi-slide deck.

Why use HTMLHero.Skill on TypingMind?

Because you install it once and use it with any model. HTMLHero.Skill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install HTMLHero.Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/YiShu5/claude-skills/tree/master/skills/HTMLHero.skill. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use HTMLHero.Skill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with HTMLHero.Skill?

As many as you like. As long as a model supports skills, you can use HTMLHero.Skill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the HTMLHero.Skill AI skill free?

Yes. It is published on GitHub by YiShu5 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇