Agent skill

Hlive Project

Structure a real multi-page HLive application in Go — the main.go entry point and net/http routing, a page/ package of page factories, reusable component functions, static asset serving, and…

MITAuto-check passedBackend & APIs

Install Hlive Project

skills CLI

$ npx skills add SamHennessy/hlive --skill hlive-project -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install SamHennessy/hlive hlive-project --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/SamHennessy/hlive.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/hlive-project .claude/skills/hlive-project && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "hlive-project" agent skill from https://github.com/SamHennessy/hlive/tree/main/plugin/skills/hlive-project into .claude/skills/hlive-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlive-project", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/SamHennessy/hlive/tree/main/plugin/skills/hlive-project

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add SamHennessy/hlive --skill hlive-project -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install SamHennessy/hlive hlive-project --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SamHennessy/hlive.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugin/skills/hlive-project .agents/skills/hlive-project && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "hlive-project" agent skill from https://github.com/SamHennessy/hlive/tree/main/plugin/skills/hlive-project into .agents/skills/hlive-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlive-project", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add SamHennessy/hlive --skill hlive-project -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install SamHennessy/hlive hlive-project --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SamHennessy/hlive.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugin/skills/hlive-project .cursor/skills/hlive-project && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "hlive-project" agent skill from https://github.com/SamHennessy/hlive/tree/main/plugin/skills/hlive-project into .cursor/skills/hlive-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlive-project", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/SamHennessy/hlive.git --path plugin/skills/hlive-project

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add SamHennessy/hlive --skill hlive-project -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install SamHennessy/hlive hlive-project --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SamHennessy/hlive.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugin/skills/hlive-project .gemini/skills/hlive-project && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "hlive-project" agent skill from https://github.com/SamHennessy/hlive/tree/main/plugin/skills/hlive-project into .gemini/skills/hlive-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlive-project", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install SamHennessy/hlive hlive-project

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add SamHennessy/hlive --skill hlive-project -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/SamHennessy/hlive.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugin/skills/hlive-project .github/skills/hlive-project && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "hlive-project" agent skill from https://github.com/SamHennessy/hlive/tree/main/plugin/skills/hlive-project into .github/skills/hlive-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlive-project", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add SamHennessy/hlive --skill hlive-project -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install SamHennessy/hlive hlive-project --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SamHennessy/hlive.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugin/skills/hlive-project .opencode/skills/hlive-project && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "hlive-project" agent skill from https://github.com/SamHennessy/hlive/tree/main/plugin/skills/hlive-project into .opencode/skills/hlive-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlive-project", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: hlive-project
GitHub stars: 101
Token cost: ~1.3k tokens
SKILL.md length: 347 words
Files: 1
Skills in repo: 5
Repo updated: Jul 2, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Structure a real multi-page HLive application in Go — the main.go entry point and net/http routing, a page/ package of page factories, reusable component functions, static asset serving, and…

Starting a new HLive project
SKILL.md covers Layout, Entry point — main.go, Pages — the page package and Reusable components, plus 4 more sections
Calls go
Organizing components across files

What it does

Hlive Project is an agent skill from SamHennessy/hlive. Structure a real multi-page HLive application in Go — the main.go entry point and net/http routing, a page/ package of page factories, reusable component functions, static asset serving, and build/run setup. Use when starting a new HLive project, adding a page or route, organizing components across files, or deciding where state and assets live (beyond the single-file example/ demos).

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs. The repository describes itself as: HLive is a server-side WebSocket based dynamic template-less view layer for Go. The licence is MIT.

When your agent uses it

Starting a new HLive project
Organizing components across files
Deciding where state and assets live (beyond the single-file example/ demos)

Example prompts

“/hlive-project”

What it can do on your machine

Read from SKILL.md and the folder at commit bc5f920. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- go
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hlive Project loads about 1.3k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 347 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~101
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from SamHennessy/hlive at commit bc5f920, republished under its MIT licence (© SamHennessy). 347 words, ~1,344 tokens.

Download SKILL.mdSave it as .claude/skills/hlive-project/SKILL.md (or your agent's skills folder).

name: hlive-project
description: Structure a real multi-page HLive application in Go — the main.go entry point and net/http routing, a page/ package of page factories, reusable component functions, static asset serving, and build/run setup. Use when starting a new HLive project, adding a page or route, organizing components across files, or deciding where state and assets live (beyond the single-file _example/ demos).

Structuring an HLive project

HLive's _example/ demos are single files to keep them readable. A real app spreads across packages. This is the recommended layout (modeled on the hlive_docs app), using hhtml for markup — see the hlive-hhtml and hlive-core skills for the building blocks.

Layout

myapp/
├── main.go              # entry point: routing + static assets
├── go.mod               # module github.com/you/myapp
├── justfile             # build/run recipes (optional)
├── page/                # one file per page; package "page"
│   ├── home.go          #   func Home() *l.Page
│   ├── about.go         #   func About() *l.Page
│   ├── components.go    #   shared unexported components: header(), footer()
│   └── demo/            #   sub-package for a group of related routes
│       └── clicker.go   #   func Clickers() http.Handler
├── src/                 # plain Go helper packages (no HLive), unit-testable
│   └── .../
└── assets/              # css/js/images served at /assets/
    └── main.css

Keep it flat — most logic lives in page/. Add a sub-package under page/ only to group a feature's routes.

Entry point — `main.go`

Use the standard library net/http; HLive's PageServer is just an http.Handler. Register each page factory, then serve static files.

package main

import (
    "log"
    "net/http"

    l "github.com/SamHennessy/hlive"
    "github.com/you/myapp/page"
    "github.com/you/myapp/page/demo"
)

func main() {
    http.Handle("/", l.NewPageServer(page.Home))
    http.Handle("/about", l.NewPageServer(page.About))
    http.Handle("/demos/clickers", demo.Clickers())

    // static assets, e.g. /assets/main.css -> ./assets/main.css
    fs := http.FileServer(http.Dir("./assets"))
    http.Handle("/assets/", http.StripPrefix("/assets/", fs))

    log.Println("listening on :3000")
    if err := http.ListenAndServe(":3000", nil); err != nil {
        log.Fatal(err)
    }
}

l.NewPageServer takes a page factory func() *l.Page. For routes that need extra wiring (their own handler, query params), expose a func() http.Handler instead (as demo.Clickers() does).

Pages — the `page` package

One exported, PascalCase factory per page, each returning *l.Page. Build the <head> (title + stylesheets) and <body> with hhtml, composing shared components:

package page

import (
    l "github.com/SamHennessy/hlive"
    . "github.com/SamHennessy/hlive/hhtml"
)

func Home() *l.Page {
    page := l.NewPage()
    page.DOM().Title().Add("MyApp — Home")
    page.DOM().Head().Add(Link(Rel("stylesheet"), Href("/assets/main.css")))

    page.DOM().Body().Add(
        Div(Class("container"),
            header(),
            Main(Class("main"),
                H1("Welcome"),
                P("Built with HLive."),
            ),
        ),
    )
    return page
}

There is no central layout wrapper; the per-page head/shell boilerplate is repeated (or factored into a small helper you call from each page). One *l.Page instance serves one connected user.

Reusable components

Shared UI is just unexported, camelCase functions returning l.Adder (the interface hhtml builders return), kept in page/components.go:

func header() l.Adder {
    return Header(Class("header"),
        Div(Class("logo"), "MyApp"),
        Nav(
            Ul(Class("nav-links"),
                Li(A(Href("/"), "Home")),
                Li(A(Href("/about"), "About")),
            ),
        ),
    )
}

Call them inside page factories: Body().Add(Div(header(), ...)).

Where state lives

Page-local reactive values: l.Box(...) / l.NewLockBox[T](...), captured in the page factory's closure and updated from l.On handlers.
Feature state that spans components or goroutines (live demos, real-time feeds): a struct holding the boxes plus methods, often with hlivekit.PubSub for fan-out. See the hlivekit skill and hlive_docs/page/demo/clicker.go.

Keep non-UI logic (parsing, calculations, data access) in plain Go packages under src/ so it's unit-testable without a browser.

Static assets

Put CSS/JS/images under assets/ and serve them as shown in main.go. Link them in each page's <head> with Link(Rel("stylesheet"), Href("/assets/...")).

Build & run

A justfile keeps commands handy (or use go directly):

build:
    go build -o ./deploy/server .

run:
    go run .

go run . from the module root is enough for local development; the server serves ./assets relative to its working directory.

Reference

hlive_docs/main.go, hlive_docs/page/home.go, hlive_docs/page/components.go, hlive_docs/page/demo/clicker.go, hlive_docs/justfile. (hlive_docs is a work-in-progress and is mid-migration to hhtml — follow the structure, and prefer hhtml for new markup.) For testing pages from a page package, see the hlive-testing skill.

Files

Just SKILL.md in plugin/skills/hlive-project of SamHennessy/hlive.

Open the folder on GitHubat commit bc5f920

Compare with similar skills

Hlive Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hlive Project compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Hlive Project this skillSamHennessy/hlive	101	—	~1.3k	Automated safety check: Pass	MIT	3 mo ago
Configuring Horizoncoollabsio/coolify	63k	4 repos	~898	Automated safety check: Pass	MIT	today
Nestjs Best Practicesrolling-scopes/rsschool-app	10k	6 repos	~1.2k	Automated safety check: Pass	MIT	5 days ago
Sub2API AdminWei-Shaw/sub2api	44k	1 repos	~717	Automated safety check: Pass	LGPL-3.0	today
Firecrawl Build Onboardingfirecrawl/firecrawl	190k	1 repos	~1.4k	Automated safety check: Notes	ISC	today
Obsidian BasesAtmosphere/atmosphere	3.8k	22 repos	~3.2k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Configuring Horizon
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
63k GitHub starsUsed in 4 repos~898 tokens
Backend & APIsAuto-check passed
Nestjs Best Practices
rolling-scopes/rsschool-app
NestJS best practices and architecture patterns for building production-ready applications.
10k GitHub starsUsed in 6 repos~1.2k tokens
Backend & APIsAuto-check passed
Sub2API Admin
Wei-Shaw/sub2api
Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.
44k GitHub starsUsed in 1 repo~717 tokens
Backend & APIsAuto-check passed
Firecrawl Build Onboarding
firecrawl/firecrawl
Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.
190k GitHub starsUsed in 1 repo~1.4k tokens
Backend & APIsAuto-check: notes
Obsidian Bases
Atmosphere/atmosphere
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.
3.8k GitHub starsUsed in 22 repos~3.2k tokens
Backend & APIsAuto-check passed
Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
63k GitHub starsUsed in 4 repos~1.9k tokens
Backend & APIsAuto-check passed

Questions about Hlive Project

What does Hlive Project do?

Structure a real multi-page HLive application in Go — the main.go entry point and net/http routing, a page/ package of page factories, reusable component functions, static asset serving, and…. Hlive Project is an agent skill from SamHennessy/hlive.go entry point and net/http routing, a page/ package of page factories, reusable component functions, static asset serving, and build/run setup.

When should I use Hlive Project?

Hlive Project fits situations like: starting a new HLive project; organizing components across files; deciding where state and assets live (beyond the single-file example/ demos).

How do I install Hlive Project in Claude Code?

Run `npx skills add SamHennessy/hlive --skill hlive-project -a claude-code`. Or copy the skill folder (plugin/skills/hlive-project in SamHennessy/hlive) into .claude/skills/hlive-project in your project. Claude Code loads it when a task matches its description.

How do I install Hlive Project in Codex?

Run `npx skills add SamHennessy/hlive --skill hlive-project -a codex`. Or copy the skill folder (plugin/skills/hlive-project in SamHennessy/hlive) into .agents/skills/hlive-project in your project. Codex loads it when a task matches its description.

Can I use Hlive Project in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SamHennessy/hlive --skill hlive-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hlive-project, .gemini/skills/hlive-project, .github/skills/hlive-project and .opencode/skills/hlive-project in your project.

What does Hlive Project need to run?

Going by SKILL.md and its folder, Hlive Project needs the command-line tools its instructions call (go).

Does Hlive Project access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Hlive Project safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hlive Project use?

Hlive Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hlive Project use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Hlive Project?

Skills that share tags, products or a category with Hlive Project: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 44k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hlive Project?

SamHennessy (a GitHub user) maintains it in SamHennessy/hlive, which has 101 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on July 2, 2026.

Source: SamHennessy/hlive on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Hlive Project

Install Hlive Project

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Structuring an HLive project

Layout

Entry point — `main.go`

Pages — the `page` package

Reusable components

Where state lives

Static assets

Build & run

Reference

Files

Compare with similar skills

Similar skills

Configuring Horizon

Nestjs Best Practices

Sub2API Admin

Firecrawl Build Onboarding

Obsidian Bases

Fortify Development

More from SamHennessy/hlive

Hlive Core

Hlive Hhtml

Hlive Testing

Hlivekit

Questions about Hlive Project

Install Hlive Project

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Structuring an HLive project

Layout

Entry point — main.go

Pages — the page package

Reusable components

Where state lives

Static assets

Build & run

Reference

Files

Compare with similar skills

Similar skills

More from SamHennessy/hlive

Related

Questions about Hlive Project

Entry point — `main.go`

Pages — the `page` package