Templ HTTP

What it does

When your agent uses it

• Connecting templ to web server
• Creating HTTP handlers
• Mentions templ server
• Serve templ components

Example prompts

• “templ server”
• “HTTP routes”
• “serve templ components”
• “/templ-http”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

1. 1Parse request input.
2. 2Build view model/data.
3. 3Render templ component with r.Context().
4. 4Handle render errors and status codes.

What it can do on your machine

Read from SKILL.md and the folder at commit 45c532e. 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

  No scripts in the folder and no shell commands in SKILL.md (its code samples are go).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • pkg.go.dev
  • templ.guide

  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

Templ HTTP loads about 591 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 176 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~52

When it runs · the whole SKILL.md, loaded when a task matches

~591

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

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 Xe/site at commit 45c532e, republished under its Zlib licence (© Xe). 176 words, ~591 tokens.

name

templ-http

description

Integrate templ components with Go HTTP server using net/http. Use when connecting templ to web server, creating HTTP handlers, mentions 'templ server', 'HTTP routes', or 'serve templ components'.

func homeHandler(w http.ResponseWriter, r *http.Request) {
    if err := components.HomePage().Render(r.Context(), w); err != nil {
        http.Error(w, "render failed", http.StatusInternalServerError)
        return
    }
}

func usersHandler(w http.ResponseWriter, r *http.Request) {
    switch r.Method {
    case http.MethodGet:
        users := listUsers(r.Context())
        _ = components.UserList(users).Render(r.Context(), w)
    default:
        http.Error(w, "method not allowed", http.StatusMethodNotAllowed)
    }
}

© Xe, Zlib. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in .agents/skills/templ-http of Xe/site.

• SKILL.md
• resources/handlers-and-routing.md
• resources/middleware-and-errors.md
• resources/request-and-response-patterns.md

Open the folder on GitHubat commit 45c532e