Install
$ agentstack add skill-fmind-dot-github-repository ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
GitHub Repository
Derive a repository's description, homepage, and topics from its codebase and apply them with gh repo edit together with solo-developer settings: squash-only merges, secure defaults, a decluttered sidebar.
Workflow
Use [gh](../gh/SKILL.md) for account selection, bounded API calls, and request serialization when needed.
- Extract metadata from the codebase:
- Project metadata: Python
pyproject.toml([project]name, description, and URLs). README.md: the first paragraphs give a one-line description under ~140 characters.- Homepage: derive from hosting, e.g.
https://.github.io/for GitHub Pages. - Topics: 3 to 6 lowercase tags for language, frameworks, tools, or domain (
agent,python,cli); letters, numbers, and hyphens only, 50 characters max, 20 per repository.
- Inspect the current state so the edit stays idempotent; stop when there is no GitHub remote or
ghis not authenticated. Resolve repository identity throughgh; never print raw remote URLs, which can contain credentials:
``bash gh auth status gh repo view --json nameWithOwner,visibility,isInOrganization,description,homepageUrl,repositoryTopics,deleteBranchOnMerge,squashMergeAllowed,mergeCommitAllowed,rebaseMergeAllowed,hasIssuesEnabled,hasProjectsEnabled,hasWikiEnabled,hasDiscussionsEnabled ``
- Build one consolidated edit: add the desired topics, remove every current topic not in that desired set, and append
--enable-issues=falseonly when the project tracks issues elsewhere. Query the repository REST payload and add the two secret-scanning flags only for a public repository or whensecurity_and_analysis.secret_scanningis present; otherwise report that the capability is unavailable and continue with the remaining settings:
``bash repository="$(gh repo view --json nameWithOwner --jq .nameWithOwner)" repository_json="$(gh api "repos/$repository")" desired_topics=(tag1 tag2 tag3) args=( --description "" --homepage "" --delete-branch-on-merge --enable-squash-merge --squash-merge-commit-message pr-title-description --enable-merge-commit=false --enable-rebase-merge=false --allow-update-branch --enable-wiki=false --enable-projects=false --enable-discussions=false ) for topic in "${desired_topics[@]}"; do args+=(--add-topic "$topic"); done while IFS= read -r topic; do [[ " ${desired_topics[*]} " == *" $topic "* ]] || args+=(--remove-topic "$topic") done &2 fi gh repo edit "$repository" "${args[@]}" ``
- Verify with the same
gh repo view --json ...call and report the fields that changed.
Gotchas
- Truncation: keep the description single-line and under ~140 characters or the GitHub UI truncates it.
- Secret scanning eligibility: public repositories are covered; private and internal repositories require an eligible GitHub Secret Protection or Advanced Security entitlement. Capability-detect instead of inferring availability from personal versus organization ownership.
- Visibility: never pass
--visibilityor--accept-visibility-change-consequencesunless the user explicitly asks.
Documentation
- gh repo edit manual
- Releases: GitHub CLI
- Companion skills: [github-pull-request](../github-pull-request/SKILL.md) (PR titles feed the squash message), [project-license](../project-scaffolding/references/project-license/GUIDE.md) (LICENSE), [project-scaffolding](../project-scaffolding/references/bootstrap.md) (bootstrap).
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.
Write a review
Versions
- v0.1.0 Imported from the upstream source.