AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Github

skill-prairieaster-ai-claude-code-skills-github · by PrairieAster-Ai

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

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-prairieaster-ai-claude-code-skills-github

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-prairieaster-ai-claude-code-skills-github)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Github? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

GitHub Wiki & Projects Skill

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

Quick Commands

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

Authentication Reference

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

| Operation | Auth method | Notes | |-----------|------------|-------| | Wiki read (clone) | SSH or HTTPS | Either works | | Wiki push | SSH only | Fine-grained PATs get 403. Always use git@github.com: URL. | | Issues, PRs, releases | gh CLI | Uses the OAuth token from gh auth login | | GitHub Projects (boards) | gh CLI + project scope | Requires 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:

``bash git clone git@github.com:/.wiki.git /-wiki ``

  1. Edit markdown files using Read/Write/Edit tools
  2. Validate — use Grep to check for broken links, TODO markers, stale content
  3. Commit and push from the wiki checkout:

``bash git -C add . && git -C commit -m "docs: " && git -C 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  --owner "$OWNER"

# Add an issue to a project
gh project item-add  --owner "$OWNER" --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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.