How do I install the Visibility skill?

Run npx skillmds@latest add lauchunchee/visibility in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Visibility safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Visibility?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Visibility free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Visibility?

lauchunchee (@lauchunchee) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Visibility by lauchunchee — Agent Skill

Name: Visibility
Author: lauchunchee

Visibility

Switches the workspace between public mode (only framework files tracked — safe to publish) and private mode (life content versioned too — git history becomes memory). Use when the user wants to share or publish the repo, make it private, commit more of their content, or check whether the repo is safe to publish.

lauchunchee ea9aa6e 3 files · 4.6 KB Updated Sep 17, 2026

File contents

Visibility — govern what git is allowed to see

Two modes, defined by which .gitignore is active. The templates live in templates/; the first line of the active .gitignore names the current mode.

public (default): fail-closed whitelist — only framework files can be committed. Safe to attach a public remote.
private: life content (area folders, inbox.md, CLAUDE.local.md, .claude/rules/) is versioned too, so git history becomes memory. private/, secrets, artifacts/, tmp/, and .claude/settings.local.json stay ignored in BOTH modes.

$ARGUMENTS is public, private, or status. With no argument, report status and ask which mode the user wants.

status

Report: current mode (first line of .gitignore), git remote -v, and the history audit result (see below). Recommend nothing unless asked.

Switching to private

Check remotes first. If any remote could be public (for GitHub remotes verify with gh repo view --json visibility when available), STOP and warn: private mode must never feed a public remote. Proceed only after the user confirms the remote is private or removes it.
Copy templates/gitignore-private over .gitignore.
Show what would now be tracked (git status --short) and offer to commit the personal layer.
If no remote exists, suggest — do not create unasked — a PRIVATE GitHub remote as an off-machine backup.

Switching to public

Copy templates/gitignore-public over .gitignore.
Re-apply ignores to the index: git rm -r --cached . then git add . (files stay on disk). Show the resulting status before any commit.
HISTORY AUDIT — the step that keeps this safe. List every path ever committed (git log --all --diff-filter=A --name-only --pretty=format:) and compare against the framework whitelist in the public template. If personal paths appear in ANY commit, say clearly:
- This branch's HISTORY still contains personal content. Untracking does not remove it from history. This branch must never be pushed anywhere public.
- The safe publish path is an orphan branch holding only framework files (git checkout --orphan public → commit framework → publish that), while the full-history branch stays private. Offer it; never rewrite history unasked.
Report "safe to publish" ONLY when the audit finds framework-only history.

Rules

Never push, change a remote's visibility, or rewrite history without explicit confirmation — show every irreversible step before taking it.
If the current .gitignore matches neither template, the mode is unknown: show the diff against the nearest template and ask before overwriting.

---name: visibilitydescription: Switches the workspace between public mode (only framework files tracked — safe to publish) and private mode (life content versioned too — git history becomes memory). Use when the user wants to share or publish the repo, make it private, commit more of their content, or check whether the repo is safe to publish.---# Visibility — govern what git is allowed to seeTwo modes, defined by which `.gitignore` is active. The templates live in`templates/`; the first line of the active `.gitignore` names the currentmode.- **public** (default): fail-closed whitelist — only framework files can be committed. Safe to attach a public remote.- **private**: life content (area folders, `inbox.md`, `CLAUDE.local.md`, `.claude/rules/`) is versioned too, so git history becomes memory. `private/`, secrets, `artifacts/`, `tmp/`, and `.claude/settings.local.json` stay ignored in BOTH modes.`$ARGUMENTS` is `public`, `private`, or `status`. With no argument, reportstatus and ask which mode the user wants.## statusReport: current mode (first line of `.gitignore`), `git remote -v`, and thehistory audit result (see below). Recommend nothing unless asked.## Switching to private1. Check remotes first. If any remote could be public (for GitHub remotes verify with `gh repo view --json visibility` when available), STOP and warn: private mode must never feed a public remote. Proceed only after the user confirms the remote is private or removes it.2. Copy `templates/gitignore-private` over `.gitignore`.3. Show what would now be tracked (`git status --short`) and offer to commit the personal layer.4. If no remote exists, suggest — do not create unasked — a PRIVATE GitHub remote as an off-machine backup.## Switching to public1. Copy `templates/gitignore-public` over `.gitignore`.2. Re-apply ignores to the index: `git rm -r --cached .` then `git add .` (files stay on disk). Show the resulting status before any commit.3. HISTORY AUDIT — the step that keeps this safe. List every path ever committed (`git log --all --diff-filter=A --name-only --pretty=format:`) and compare against the framework whitelist in the public template. If personal paths appear in ANY commit, say clearly: - This branch's HISTORY still contains personal content. Untracking does not remove it from history. This branch must never be pushed anywhere public. - The safe publish path is an orphan branch holding only framework files (`git checkout --orphan public` → commit framework → publish that), while the full-history branch stays private. Offer it; never rewrite history unasked.4. Report "safe to publish" ONLY when the audit finds framework-only history.## Rules- Never push, change a remote's visibility, or rewrite history without explicit confirmation — show every irreversible step before taking it.- If the current `.gitignore` matches neither template, the mode is unknown: show the diff against the nearest template and ask before overwriting.

Frequently asked questions