hashtree-git skill
Publish, clone, and share Git repositories using htree URLs without requiring a hosting account.
- GitHub stars
- 12
- Files
- 2
- Last commit
- Nov 11, 2026
- License
- —
- Allowed tools
- —
What does the hashtree-git skill do?
hashtree-git is an agent skill. Publish, clone, and share Git repositories using htree URLs without requiring a hosting account.
Summary generated from the skill's SKILL.md.
About the hashtree-git skill
Publishing and sharing Git repositories without a hosting account is what this skill enables through Hashtree and Iris Git. Developers can use it when they need to distribute code via htree URLs or collaborate using account-free Git publishing. An agent should load this tool when a user requests to push a local repository to a public, link-visible, or private remote using the git-remote-htree extension.
The skill relies on the htree CLI and standard Git commands to manage identities and remotes. It produces shareable clone URLs, such as htree://PUBLIC_NPUB/REPO_NAME, and browser-accessible links. It handles different visibility levels, including public repositories, link-visible repositories using a secret #k= fragment, and private repositories that require the author's identity for decryption. Users must manage their own signing keys and persistent data directories to maintain a consistent profile across different sessions.
What an agent can do with it
- 1Share a private repositorySet up a private repository that only the author can decrypt and access.
- 2Collaborate via forkingClone a public repository, create a fork under a new identity, and share the new URL for review.
- 3Verify remote accessibilityConfirm that a repository is actually readable by an independent user by performing a test clone.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the hashtree-git skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the hashtree-git skill in Plugin
/plugin marketplace add mmalmi/hashtree /plugin install hashtree-git@hashtree-plugins
Install the hashtree-git skill in Claude Code
~/.claude/skills/hashtree-git/SKILL.md
$ npx degit mmalmi/hashtree/plugins/hashtree-git/skills/hashtree-git ~/.claude/skills/hashtree-gitInstall the hashtree-git skill in Claude Code (project)
.claude/skills/hashtree-git/SKILL.md
$ npx degit mmalmi/hashtree/plugins/hashtree-git/skills/hashtree-git .claude/skills/hashtree-gitInstall the hashtree-git skill in Codex
~/.agents/skills/hashtree-git/SKILL.md
$ npx degit mmalmi/hashtree/plugins/hashtree-git/skills/hashtree-git ~/.agents/skills/hashtree-gitInstall the hashtree-git skill in Gemini CLI
~/.gemini/skills/hashtree-git/SKILL.md
$ npx degit mmalmi/hashtree/plugins/hashtree-git/skills/hashtree-git ~/.gemini/skills/hashtree-gitInstall the hashtree-git skill in Claude.ai
npx degit mmalmi/hashtree/plugins/hashtree-git/skills/hashtree-git hashtree-git && zip -r hashtree-git.zip hashtree-git # claude.ai → Customize → Skills → + → Create skill → Upload a skill → hashtree-git.zip
Automated checks
Ran Nov 16, 2026Full report →Not verified yet. A skill needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemmalmi/hashtree/plugins/hashtree-git/skills/hashtree-git is public and reachablegithub.com/mmalmi/hashtree/tree/HEAD/plugins/hashtree-git/sk ↗Pass
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit 2026-11-11github.com/mmalmi/hashtree/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/mmalmi/hashtree/blob/HEAD/plugins/hashtree-git/sk ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/mmalmi/hashtree/blob/HEAD/plugins/hashtree-git/sk ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 85 linesgithub.com/mmalmi/hashtree/blob/HEAD/plugins/hashtree-git/sk ↗Pass
SKILL.md
View on GitHubHashtree Git
Use ordinary Git with git-remote-htree. htree manages the local identity and
optional daemon. A daemon is not required for basic Git operations.
Prepare
- Check
htree --versionandcommand -v git-remote-htree. Install released binaries using the project's installation guide, orcargo install hashtree-cli git-remote-htreeif a Rust build is appropriate. - Use the identity the user intends.
htree usergenerates a key if absent and shows public identities, with the default first. For an agent's independent profile, setHTREE_CONFIG_DIRandHTREE_DATA_DIRto persistent private directories outside repositories before invoking either CLI or Git. Keep the settings consistent across runs. Never print, upload, or commit thekeysfile; each writer gets its own key. - Confirm the destination and visibility from the user's request before a
first publication. An unqualified
htree://remote is public, including Git history and author metadata. Existing authorization to publish is sufficient; a clone request alone does not authorize a push.
Publish and read
For an existing repository, inspect git status, git remote -v, and the branch
to publish. Preserve existing remotes and uncommitted work. Add a distinct remote
name when htree is already taken:
git remote add htree htree://self/REPO_NAME
git push htree HEAD
self resolves to the current profile's signing identity. Get the default
public identity from the first field of the first line of htree user and return
these public URLs after a successful push:
- Clone:
htree://PUBLIC_NPUB/REPO_NAME - Browser:
https://git.iris.to/#/PUBLIC_NPUB/REPO_NAME
Use a simple repository name or encode URL path segments correctly. Never share
htree://self/… as another user's clone URL.
git clone htree://PUBLIC_NPUB/REPO_NAME
For a first-use check, clone with a separate profile and empty data directory (or
on another machine), compare git rev-parse HEAD with the published commit, and
read a known file. Report the actual commit and any failed step. A cached local
read does not prove an independent reader can fetch the repository.
Visibility and collaboration
- Public: no fragment. Inspect the history for unintended content before publishing a new repository.
- Link-visible: use
#link-visiblefor setup. The first invocation generates a secret URL and instructions; set the remote to that#k=…URL, then push again. Setup alone is not a publication. Treat the URL as a read credential; never include it in public reports. Preserve the key when sharing privately. - Private:
#privatepermits the author's identity to decrypt. Do not convert to public or link-visible just to make another reader's clone work.
For collaboration, clone the author's public URL, publish a fork to your own
htree://self/FORK_NAME, and share the public fork URL and branch for review.
htree pr create --help documents optional pull-request announcements. Forking
does not grant writes to the original. Do not share signing keys between agents
or force-push over unexpected remote refs. Fetch by the author's public identity;
do not use a self publish remote as an upstream to pull/rebase from.
Completion and failures
Report the published commit, appropriate shareable URL, and independent-read result. Distinguish local commits, successful pushes, and verified remote reads. Preserve failed work for retry. A relay timeout is not proof a repository is absent. Storage operators control availability and retention, so promise no unlimited storage or permanent hosting.
For the complete first-use walkthrough, see Git for humans and agents.
Files in this skill
2hashtree-git skill questions
How do I install the hashtree-git skill in Claude Code?
Run npx degit mmalmi/hashtree/plugins/hashtree-git/skills/hashtree-git ~/.claude/skills/hashtree-git. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the hashtree-git skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How do I publish a repository using Hashtree?
You can add a remote using the htree protocol and push your HEAD, for example: git remote add htree htree://self/REPO_NAME followed by git push htree HEAD.
Does Hashtree require a daemon to run?
A daemon is not necessary for basic Git operations, though htree can manage an optional daemon.