Open Source Release
Use when a project may go public. Repo and licence.
Install
npx skills add SamueleBassoli/hermes-fleet-apps --skill open-source-releasegit clone --depth 1 https://github.com/SamueleBassoli/hermes-fleet-apps.git /tmp/hermes-fleet-apps
mkdir -p ~/.claude/skills
cp -r /tmp/hermes-fleet-apps/roles/docs/skills/open-source-release ~/.claude/skills/open-source-releasePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Open Source Release How a personal tool becomes a public repo without leaking anything, without a licence surprise, and without a rewrite at the end. Assume the owner is not a developer and has an empty GitHub account. They will not remember repo hygiene and should not have to. The building agent (the coder role) owns every git and GitHub decision, does it from the first commit, and reports what it did rather than asking. This skill is about *shipping*. The design method itself lives elsewhere; load both when a build is intended to be published. ## The ladder ``` local git ──▶ private GitHub ──▶ public from commit 1 once it runs once it is stable and licence-clean ``` Never start at the public end. A repo that was private first can be cleaned. A repo that was public first has its mistakes in other people's clones forever. Decide the ladder **at project start**, out loud, in one line. "Public eventually" changes what goes into commit 1; discovering it later means an audit and possibly a history rewrite. ## Step 1 — first commit, before the first source file Run `git init` when the project folder is created, not when the code works. History that starts late cannot show how the thing was built. The first commit contains, always: - **`.gitignore`** covering the virtualenv directory, `__pycache__`, generated databases and state files, run journals and logs, downloaded model weights or other large
Details
- Skill name
open-source-release- Repository
- SamueleBassoli/hermes-fleet-apps
- Path
roles/docs/skills/open-source-release/SKILL.md- License
- MIT
- Repo updated
- 31 October 2026
FAQ
What does the Open Source Release skill do?
Use when a project may go public. Repo and licence.
How do I install the Open Source Release skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add SamueleBassoli/hermes-fleet-apps --skill open-source-release. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Open Source Release popular?
It lives in SamueleBassoli/hermes-fleet-apps, which has 44 GitHub stars and 0 forks.
Related skills
Agent Facing CLI
44SamueleBassoli/hermes-fleet-apps
Use when an agent will drive a CLI. Contract test first.
Agent Fleet Design
44SamueleBassoli/hermes-fleet-apps
Use when adding, backing up, or driving the agent fleet.
Agent Identity Setup
44SamueleBassoli/hermes-fleet-apps
Use when setting up or resetting agent SOUL, memory, skills.
Acos Meta
48frankxai/claude-skills-library
ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.
Code Generated Video
44SamueleBassoli/hermes-fleet-apps
Use when a short teaser is asked for in the ff-tracking style: every pixel and sound from code.
API Documentation
430xranx/agentbrief
Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.