atlassian-browser-authentication
Use when authenticating to Atlassian (Jira, Confluence) — opens a local browser for sign-in/MFA and saves a reusable Playwright auth state (session, cookies).
76
93%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 a narrow, specific capability. It leads with an explicit 'Use when' trigger clause, names the specific platforms (Jira, Confluence), and describes the concrete mechanism (browser-based auth with Playwright state persistence). The only minor note is it could mention file formats or paths for the saved auth state, but this is not necessary for skill selection.
| 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'. Users needing Atlassian authentication would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche of Atlassian authentication via Playwright browser automation. Unlikely to conflict with general Jira/Confluence task skills or other authentication skills due to the specific mechanism described. | 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-structured, concise skill that clearly communicates how to authenticate to Atlassian via a browser flow. Its strengths are brevity, actionable commands, and clean organization. The main weakness is the lack of error handling guidance or validation steps for when authentication fails or the state file is corrupted.
Suggestions
Add a brief error-handling note: what to do if the script exits with an error or the state file is missing/invalid (e.g., retry with --force).
Consider adding a validation step to verify the state file is usable before proceeding with downstream tasks (e.g., check file exists and is recent).
| 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 workflow is present (set SKILL_DIR, run command, wait for user, get output) but lacks explicit validation/error handling. There's no guidance on what to do if authentication fails, if the state file is invalid, or how to verify the cached state is actually fresh before deciding to skip re-auth. | 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). References to `$SKILL_DIR/scripts/browser.py` are appropriate and one level deep. | 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.
- Repository
- freneticdisc/grammaire
- Commit
1ce64c0
- 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.