grammaire/atlassian-browser-authentication
Authenticate to Atlassian by opening a local browser for sign-in/MFA and saving reusable Playwright auth state.
95
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that clearly communicates both what the skill does and when to use it. It leads with an explicit 'Use when' clause, names specific products (Jira, Confluence), and describes concrete technical actions (browser sign-in, saving Playwright auth state). The description is concise yet comprehensive, with excellent trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'opens a local browser for sign-in/MFA', 'saves a reusable Playwright auth state (session, cookies)'. These are specific, actionable capabilities rather than vague language. | 3 / 3 |
Completeness | Explicitly answers both 'what' (opens browser for sign-in/MFA, saves Playwright auth state) and 'when' (starts with 'Use when authenticating to Atlassian (Jira, Confluence)'). The 'Use when...' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'authenticating', 'Atlassian', 'Jira', 'Confluence', 'sign-in', 'MFA', 'browser', 'Playwright', 'auth state', 'session', 'cookies'. Good coverage of terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche of Atlassian authentication via Playwright browser automation. The combination of Atlassian + Playwright + auth state makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that clearly instructs Claude on how to perform Atlassian browser authentication. Its strengths are brevity, actionable commands, and clear structure. The main weakness is the lack of error handling guidance or validation steps—there's no mention of what to do if authentication fails, times out, or produces an invalid state file.
Suggestions
Add a brief validation step after the script runs, e.g., check that the state file exists and is non-empty, with guidance on what to do if it fails.
Include a note on error scenarios (e.g., user cancels login, MFA timeout) and how Claude should respond.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—rules, inputs, run commands, and output format. No unnecessary explanations of what Atlassian is or how Playwright works. | 3 / 3 |
Actionability | Provides specific, executable commands (`uv run "$SKILL_DIR/scripts/browser.py" "<URL>"` with and without `--force`), clear input parameters, and exact expected output format. Copy-paste ready. | 3 / 3 |
Workflow Clarity | The steps are present but lack explicit validation checkpoints. There's no guidance on what to do if authentication fails, if the cached state is stale, or how to verify the state file is valid before using it in subsequent operations. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized into clear sections (Rules, Inputs, Run, Output). No bundle files are provided, but none seem necessary for this straightforward authentication flow. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents