Documentation menu
Introduction
Issuing certificates
Security
Reference

Home › Docs › Agent Skill

Agent Skill

homepki ships an Agent Skill compiled into the binary. Once installed, AI coding tools use homepki whenever a script, demo or test needs TLS or mTLS material, instead of hand-written openssl commands or ad-hoc self-signed certificates.

What it is

The skill is a single Markdown file, SKILL.md, with a short description that tells the tool when to load it and a body that tells it how to use homepki. It is the SKILL.md at the root of the repository, embedded in the binary at build time, so the installed copy always matches the installed release. Nothing is downloaded.

Install

$ homepki skill install
Installed homepki Agent Skill → ~/.claude/skills/homepki/SKILL.md
Start a new AI coding session to pick it up.

Start a new agent session after installing: tools read their skills directory at start-up.

CommandWhat it does
homepki skill installWrite the skill to Claude Code's user skills directory. If a copy exists, print its path and leave it unchanged.
homepki skill install --forceOverwrite an existing copy.
homepki skill install --printWrite the skill to stdout instead, for another tool or a project-level skills directory.
homepki skill install --claude=falseDisable the Claude Code target. Without --print this is an error: there is no other target yet.
homepki skill pathPrint the install path, ~/.claude/skills/homepki/SKILL.md.
 
# a project-level skill, committed with the project
$ mkdir -p .claude/skills/homepki
$ homepki skill install --print > .claude/skills/homepki/SKILL.md

What it covers

The skill documents behaviour that --help does not show, so an agent gets it right the first time:

  • the three tiers, how subjects and file names are derived, and the paths to wire into a recipe;
  • key types, validity, name constraints and Subject Alternative Names, including quoting * for zsh;
  • list -o json and a jq check for broken chains, which is the reliable signal in scripts;
  • trust stores and when sudo prompts, so an unattended agent avoids hanging on a password;
  • signing external CSRs, PKCS#12 bundles and CRL revocation;
  • overwrite protection, what --force orphans on each tier, and how to use a throwaway workdir instead;
  • verifying by hand with openssl, and when not to use homepki.

Updating after an upgrade

The installed copy does not change when you upgrade homepki. Overwrite it so the skill describes the new release:

$ brew update && brew upgrade --cask homepki
$ homepki skill install --force
✓

Edit SKILL.md in the repository, never an installed copy. The next skill install --force replaces any local edits.

← PreviousGo package