repo-sanitization

Files (1)

• SKILL.md

SKILL.md (first lines)

# Repository Sanitization

Use this before publishing private work as open source.

## Workflow

1. Create a staging copy; never publish the live private directory directly.
2. Remove `.env`, database files, credentials, logs, cache, uploads, browser profiles, and private config.
3. Search for names, phone numbers, emails, IPs, tokens, and customer references.
4. Replace project-specific prompts with generic examples.
5. Run a secret scan before the first commit.
6. Review the final repository in GitHub after pushing.

## Reject conditions

Do not publish if the repository still contains:

- API keys or bot tokens;
- OAuth files;
- private customer data;
- production server details;
- personal memories;
- commercial strategy or client-specific prompts.

## Verification

Run a pattern scan and manually inspect the README, docs, examples, and commit diff.

From aims1425-lab/hermes-agent-public-skills, MIT.

More from aims1425-lab/hermes-agent-public-skills