agentsclimarketplace

Rk remote init

Skill Sixz-AI/repo-knowledge/skills/rk-remote-init

Initialize remote sync for the knowledge base. Sets up ~/.repo-knowledge/ as a git repository, configures a user-provided remote URL, links to the main branch, and either pushes local data (first machine) or pulls existing data (subsequent machines). Use when user says 'set up remote sync', 'connect remote repo', 'init remote', 'rk-remote-init', or provides a git URL for syncing the knowledge base.From its SKILL.md

Install
npx -y skills add Sixz-AI/repo-knowledge --skill rk-remote-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, as published. Nobody here has run it

RK Remote Init — Initialize Remote Sync

Link the local knowledge base to a user-provided remote git repository.

Security warning: The remote repository will contain documentation that includes code snippets from your indexed projects. Always use a private repository.

Input

Step 1: Resolve home directory (cross-platform)

python3 -c "import os; print(os.path.expanduser('~'))"

Store result as {HOME}. Use {HOME}/.repo-knowledge as the base path for all operations.

Step 2: Ensure base directory exists

Use the Write tool to create {HOME}/.repo-knowledge/_registry.md if it does not already exist (this also creates the directory). Content if creating new:

# RepoKnowledge Registry

| Project | Git URL | Last Update | Docs |
|---------|---------|-------------|------|

Step 3: Check if already a git repo

git -C {HOME}/.repo-knowledge rev-parse --git-dir 2>/dev/null && echo "yes" || echo "no"

If not a git repo, initialize:

git -C {HOME}/.repo-knowledge init
git -C {HOME}/.repo-knowledge checkout -b main 2>/dev/null || true

Step 4: Create .gitignore

Use Write tool to create {HOME}/.repo-knowledge/.gitignore:

_repos/
*.tmp

Step 5: Configure remote

git -C {HOME}/.repo-knowledge remote add origin <git-url> 2>/dev/null || \
git -C {HOME}/.repo-knowledge remote set-url origin <git-url>

Step 6: Detect whether remote already has data

git -C {HOME}/.repo-knowledge fetch origin main 2>/dev/null && echo "has_data" || echo "empty"

If remote already has data (subsequent machine setup):

Run the full merge flow from rk-pull (Steps 3–7 of rk-pull) to bring remote knowledge into local before pushing.

Then:

git -C {HOME}/.repo-knowledge push -u origin main

If remote is empty (first machine):

git -C {HOME}/.repo-knowledge add -A
git -C {HOME}/.repo-knowledge commit -m "init: initial knowledge base" --allow-empty
git -C {HOME}/.repo-knowledge push -u origin main

Step 7: Save remote config

Use Write tool to write {HOME}/.repo-knowledge/_remote.md:

remote: <git-url>
initialized: {YYYY-MM-DD}

Step 8: Confirm

Tell the user:

  • Remote URL configured
  • Whether this was a first-time init (pushed local) or a new machine (pulled remote)
  • Next step: rk-update will now auto-sync after each run

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.