CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/gh-auth-isolation/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is highly actionable with concrete executable commands and clear, sequenced workflows supported by good and bad examples, with only minor room to tighten prose and integrate verification into each main workflow.

DimensionReasoningScore

Conciseness

The body is mostly lean command-driven content with brief, relevant context; minor prose such as 'Why this works' explanations and the Context preamble could be trimmed slightly.

4 / 5

Actionability

Provides copy-paste-ready, executable commands (gh auth status, gh auth token --user, token-authenticated git push) with concrete examples covering the common EMU-vs-personal cases.

5 / 5

Workflow Clarity

Sequences multi-step operations with numbered inline comments and includes verification and cleanup checkpoints ('Check before you push', 'Clean up — don't leave token in remote URL'), though validation is shown in a separate example rather than integrated into each main workflow.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Context, Patterns, Examples, Anti-Patterns) with no bundle files and all content self-contained; structure is good though everything lives inline with no one-level-deep references to split out advanced material.

4 / 5

Total

17

/

20

Passed

Description

57%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 is distinctive and names a clear, specific niche, but it lacks an explicit 'when to use' trigger and enumerates only a single generic action, leaving both completeness and trigger coverage moderate.

Suggestions

Add an explicit 'Use when...' clause stating the trigger conditions, e.g. 'Use when an agent needs to push to personal repos or create PRs from forks while its default gh auth is an EMU account'.

Replace the generic verb 'manage' with concrete actions such as 'detect the active identity, extract per-account tokens, and push or open PRs as a specific user'.

Add natural trigger synonyms users would say ('multiple GitHub accounts', 'switch GitHub accounts', 'EMU and personal auth') to improve keyword coverage.

DimensionReasoningScore

Specificity

Names a specific domain ('multiple GitHub identities (EMU + personal) in agent workflows') with the concrete action 'manage', but lists only one generic action verb rather than multiple concrete operations.

3 / 5

Completeness

Clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes relevant keywords ('GitHub identities', 'EMU', 'personal', 'agent workflows') but omits common natural variations a user might say like 'accounts', 'authentication', 'switching', or 'tokens'.

3 / 5

Distinctiveness Conflict Risk

Targets a highly specific niche (EMU + personal GitHub identity isolation in agent workflows) with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
Reviewed

Table of Contents

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.