Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
Open Source Release
Convert a private repository to public open-source. Use when making a repo public, sanitizing personal info from code/docs/git history, or preparing a projec...
skill openclawclawhub Free
Convert a private repository to public open-source. Use when making a repo public, sanitizing personal info from code/docs/git history, or preparing a projec...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.1.0
Provenance
- Publisher
- jini92
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Open Source Release
Safely convert a private repo to public by sanitizing personal data and cleaning history.
Pre-flight Checklist
Scan source code โ search for: Absolute paths: C:\Users\, home directory references Usernames: OS-specific account names Internal hostnames / port names API keys / tokens: .env, hardcoded secrets Email / phone numbers in commit author config Check cached artifacts โ ensure .gitignore covers: Binary caches (.pkl, .db, checksums.json) __pycache__/, node_modules/, .env, *.egg-info/ Project-specific cache directories
Step 1: Code Scan
# Find hardcoded paths and usernames Get-ChildItem -Recurse -Include "*.py","*.ps1","*.js","*.ts" | Select-String -Pattern "C:\\Users|/home/|your-username" -SimpleMatch | Where-Object { $_.Path -notmatch "__pycache__|node_modules|\.git" } Fix: replace with environment variables (os.environ.get / process.env) and add a .env.example.
Step 2: Docs Scan
Get-ChildItem -Recurse -Include "*.md","*.txt","*.yaml","*.yml" | Select-String -Pattern "C:\\Users|/home/|your-username" -SimpleMatch | Where-Object { $_.Path -notmatch "node_modules|\.git" } Replace personal paths with generic placeholders ($VAULT_PATH, ~/vault, etc.).
Step 3: Git History Analysis
git log --all -p | Select-String -Pattern "SENSITIVE_TERM" | Select-Object -First 50 git log --all --diff-filter=A -- "cache/*" Choose a strategy: < 50 commits + cache only in history โ Option B (clean push) Large history with sensitive data โ Option A (BFG Repo Cleaner / git filter-repo) History is fine, just old paths โ Option C (leave as-is)
Step 4: Clean Push (Option B)
git checkout --orphan clean-main git add -A git commit -m "feat: initial public release" git remote set-url origin https://github.com/{owner}/{repo}.git # verify no token in URL! git branch -M main git push origin main --force git push origin --delete {old-branch}
Step 5: Make Public
gh repo edit {owner}/{repo} --visibility public --accept-visibility-change-consequences --description "Short description"
Step 6: Verify
# Final scan for sensitive strings Get-ChildItem -Recurse -Include "*.py","*.md","*.yaml","*.js","*.ts" | Select-String -Pattern "SENSITIVE_TERM" -SimpleMatch | Where-Object { $_.Path -notmatch "__pycache__|node_modules|\.git" } # Confirm remote URL has no token git remote -v # Confirm visibility gh repo view {owner}/{repo} --json visibility
Step 7: Post-Release Housekeeping (Optional)
Add issue tracking to HEARTBEAT.md Update memory/{project}.md with release notes
Gotchas
Never include tokens in git remote URLs โ always verify before push Binary caches not covered by .gitignore may already be in history โ check carefully Encoding issues on Windows โ use UTF-8 explicitly in PowerShell/Python Your GitHub username is already public โ that is fine to leave as-is Never commit .env files โ add to .gitignore if not already there
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md