agentleFS
Sign inStart free
PrairieAster-AiPrairieAster-Ai/quality-butler/skills/github-wiki/SKILL.md

github-wiki

Skill0 starsChanged 4 months agoApache-2.0View on GitHub

Manage GitHub Wiki and GitHub Projects for the current repo. Knows the authentication quirks for each (SSH for Wiki push, OAuth scopes for Projects).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Project scope error: Run gh auth refresh -s read:project,project.

    line 82
  2. Distinctive:

    Stale wiki clone: Always git pull before editing if the clone already exists.

    line 84

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub Wiki & Projects Skill

Assists with GitHub Wiki editing and GitHub Project board management for the current repository.

Quick Commands

  • /github-wiki wiki list — Clone the wiki and list all pages
  • /github-wiki wiki edit <page> — Edit a specific wiki page
  • /github-wiki wiki create <page> — Create a new wiki page
  • /github-wiki projects list — List GitHub Projects for this repo
  • /github-wiki projects view <number> — View a specific project board

Authentication Reference

GitHub uses three different auth mechanisms depending on the operation. Getting these wrong produces confusing 403 errors.

OperationAuth methodNotes
Wiki read (clone)SSH or HTTPSEither works
Wiki pushSSH onlyFine-grained PATs get 403. Always use git@github.com: URL.
Issues, PRs, releasesgh CLIUses the OAuth token from gh auth login
GitHub Projects (boards)gh CLI + project scopeRequires gh auth refresh -s read:project,project first

Before Wiki operations

  1. Verify SSH: ssh -T git@github.com
  2. Get the repo's remote URL: git remote get-url origin
  3. Construct the wiki SSH URL by replacing .git with .wiki.git and ensuring it starts with git@github.com:
  4. Clone into your system's temp directory (e.g., /tmp/ on Linux/macOS, %TEMP% on Windows)

Before GitHub Projects operations

The default gh OAuth token lacks project scopes. If gh project list fails with a scopes error, tell the user:

Your gh token needs the project scope. Run:

gh auth refresh -s read:project,project

Wiki Workflow

  1. Clone the wiki into a temp directory using the SSH URL:
    git clone git@github.com:<owner>/<repo>.wiki.git <scratchpad-or-temp-dir>/<project>-wiki
  2. Edit markdown files using Read/Write/Edit tools
  3. Validate — use Grep to check for broken links, TODO markers, stale content
  4. Commit and push from the wiki checkout:
    git -C <wiki-dir> add . && git -C <wiki-dir> commit -m "docs: <description>" && git -C <wiki-dir> push origin master

Wiki repos have a single master branch and no PR workflow — commits push directly.

GitHub Projects Workflow

Detect the repo owner from gh repo view:

OWNER=$(gh repo view --json owner --jq '.owner.login')

# List projects
gh project list --owner "$OWNER"

# View a project
gh project view <number> --owner "$OWNER"

# Add an issue to a project
gh project item-add <project-number> --owner "$OWNER" --url <issue-url>

Common Pitfalls

  • Wiki push 403: You used HTTPS or a fine-grained token. Switch to SSH.
  • Project scope error: Run gh auth refresh -s read:project,project.
  • Wiki branch confusion: Wiki repos use master, not main.
  • Stale wiki clone: Always git pull before editing if the clone already exists.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free