Name: github-multi-account
Rating: 62.4 (1 reviews)
Author: bradygaster

github-multi-account

Detect and set up account-locked gh aliases for multi-account GitHub. The AI reads this skill, detects accounts, asks the user which is personal/work, and runs the setup automatically.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/github-multi-account/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete, executable PowerShell and a clear detect → ask → setup → verify → inform sequence including a verification step. Main weaknesses are the triple duplication of the alias function definitions, the absence of error-recovery guidance for the semi-invasive profile/PATH modifications, and the absence of a rollback path if verification fails.

Suggestions

Add a short error-recovery note after Step 4 (e.g., what to check if ghp/ghw is not recognized — new session required for PATH, profile reload) to close the workflow_clarity gap toward anchor 5.

Consolidate the gh-personal/gh-work function definitions to a single occurrence referenced by the session-load and squad-agent sections, removing duplicated code blocks and trimming tokens.

Clarify that the "Repo-Specific Account Binding" section applies only to the bradygaster/squad repository or generalize it, since it currently hardcodes usernames that conflict with the dynamic setup in Steps 1–3.

Dimension	Reasoning	Score
Conciseness	No over-explanation of concepts Claude already knows; every section is operational. Not a 5 because the gh-personal/gh-work function definitions appear three times (profile block, "Load in current session" block, and "For Squad Agents"), which is trimmable duplication.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance: exact detection command (`gh auth status`), a complete PowerShell setup script, and concrete verification commands (`ghp api user --jq '.login'`). Placeholders are clearly marked for the agent to fill with actual usernames.	5 / 5
Workflow Clarity	Steps 1–5 are clearly sequenced with an explicit verification checkpoint (Step 4 shows expected outputs). Not a 5 because there is no error-recovery loop if verification fails, and the profile/PATH mutations — which are semi-invasive — lack rollback or failure handling guidance.	4 / 5
Progressive Disclosure	Well-organized sections (When to Activate, What to Do, After Setup, Repo-Specific Binding, For Squad Agents) with no external files needed. Not a 5 because the body is ~87 lines — above the under-50-line simple-skill exception — and contains content (duplicated alias definitions, repo-specific binding) that could be consolidated.	4 / 5
	Total	17 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states concrete, specific actions in a distinct niche, but omits any "when to use" trigger guidance, which both caps completeness and weakens its usefulness for skill selection. Adding an explicit activation condition (e.g., when the user has multiple GitHub accounts or mentions switching between them) would resolve the main weakness.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user has multiple GitHub accounts, mentions work/personal account switching, or `gh auth status` shows 2+ accounts" — this directly addresses the completeness cap.

Add natural trigger variations users would say, such as "multiple GitHub accounts", "personal and work accounts", or "gh auth switch", to raise trigger term coverage.

State capabilities in terms of what the skill provides (persistent ghp/ghw aliases across PowerShell and CMD, PATH setup, verification) rather than narrating the AI's process steps, which reads as meta-description rather than capability coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Detect and set up account-locked gh aliases", "detects accounts, asks the user which is personal/work, and runs the setup" — with only minor coverage gaps. Not a 5 because the actions describe the AI's process rather than comprehensively covering the skill's capabilities.	4 / 5
Completeness	The "what" is clear ("Detect and set up account-locked gh aliases for multi-account GitHub") but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guideline.	3 / 5
Trigger Term Quality	"multi-account GitHub", "gh aliases", and "personal/work" are natural terms users would say. Missing a few common variations such as "multiple GitHub accounts" or "gh auth", keeping it below anchor 5.	4 / 5
Distinctiveness Conflict Risk	"account-locked gh aliases for multi-account GitHub" carves a clear niche that few skills share. Not a 5 because it could still overlap with generic GitHub/gh workflow skills given the missing explicit trigger context.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: bradygaster/squad
Path: .copilot/skills/github-multi-account/SKILL.md
Commit: 29e69f5

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.