CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wifi-password-update

Runs the full Bloom Guest Wi-Fi password pipeline for this repo — Google Sheet to generated posts to deployed site. Use this whenever the user wants to change, add, rotate, or check guest Wi-Fi passwords, mentions the password spreadsheet or "source of truth" sheet, asks to run ./update-passwords or update-passwords, asks to fill in a month or date range of passwords, asks why the site shows a stale or missing password, or asks to deploy/publish/redeploy bloomwifi.today. Also use it when the user just names a password and a period ("make August 6NHTtwFN", "set next week to X") without naming any tooling, since that always means this pipeline.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An excellent operational skill document: every step is executable, validation and error-recovery loops are explicit and tied to real observed failure modes, and the human-in-the-loop constraint is handled with unusual clarity. The remaining gaps are modest — some narrative padding and time-bound example dates hurt conciseness slightly, and the deploy-troubleshooting and verification details could be offloaded to reference files to tighten the main body.

Suggestions

Trim the narrative framing (e.g., 'The one constraint that shapes everything' prose and the 'Worth saying out loud' paragraph) to bare operational directives, and replace hardcoded example dates like 2026-08-03 with a parameterized placeholder so the guidance does not age.

Move the GitHub Actions troubleshooting (transient HttpError rerun procedure, job-ID refetching) and the QR recomputation recipe into a references/ file (e.g., references/deploy-verification.md) to shorten the always-loaded SKILL.md body.

Consider a one-line quick-reference summary of the 8-step pipeline at the top so the overall flow is graspable before the detailed per-step content.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational knowledge Claude could not infer (Drive connector cannot edit files, jekyll binstub PATH failure, %e double-space padding, transient Pages HttpError, rerun job-ID semantics), but carries minor trimmable padding — the narrative framing of "The one constraint that shapes everything" and the "Worth saying out loud" judgment paragraph — and embeds time-sensitive dates (2026-08 examples) outside any deprecated section, matching anchor 4 rather than 5.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: the exact curl export URL the script uses, direct script invocations with both flag modes, the `JEKYLL=$(gem contents jekyll | grep 'exe/jekyll$')` workaround for a real environment failure, grep verifications with expected counts, live-site curl checks, parameterized MCP tool calls, and matching commit-message examples.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints and feedback loops: interpreting each summary-line outcome in step 4, the delete-and-rebuild `git diff --quiet` source-of-truth check in step 5, grep-verifying the built page in step 6, and in step 8 verifying the live site (not the green check) plus error recovery for the known transient deploy failure including re-fetching new job IDs after a rerun. The batch regeneration step includes validation, so the missing-validation cap does not apply.

5 / 5

Progressive Disclosure

Well-sectioned body with the one bundle script (scripts/sheet_rows.rb, verified to exist) properly externalized — usage shown inline, implementation in the script. However, everything else (deploy/GitHub Actions troubleshooting, the QR verification recipe, the environment quirks) is inlined in a single ~190-line file with no references/ split, matching anchor 4's 'minor organization gaps' rather than the clean overview-plus-references structure of anchor 5.

4 / 5

Total

18

/

20

Passed

Description

95%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.

A strong description that clearly states a concrete pipeline capability and gives exceptionally rich, natural trigger coverage including example user utterances. Its only weakness is that the capability statement is one composite pipeline description rather than an enumerated action list, and its length sits at the upper edge of what 'concise and clear' rewards — though nearly every clause carries trigger value rather than padding.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions ("change, add, rotate, or check guest Wi-Fi passwords", "fill in a month or date range", "deploy/publish/redeploy"), but the core 'what' is a single composite pipeline statement ("Runs the full Bloom Guest Wi-Fi password pipeline — Google Sheet to generated posts to deployed site") rather than a comprehensive enumeration of discrete capabilities, matching anchor 4 rather than 5.

4 / 5

Completeness

It explicitly answers both questions: what ("Runs the full Bloom Guest Wi-Fi password pipeline for this repo — Google Sheet to generated posts to deployed site") and when ("Use this whenever the user wants to change, add, rotate, or check guest Wi-Fi passwords..."), with concrete trigger phrases throughout. Uses third person ("Runs"), consistent with the voice guideline.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage including synonyms and verbatim user phrasings: "guest Wi-Fi passwords", "password spreadsheet", "source of truth" sheet, "stale or missing password", "deploy/publish/redeploy bloomwifi.today", and example utterances like "make August 6NHTtwFN" and "set next week to X" — exactly what the anchor-5 example demonstrates.

5 / 5

Distinctiveness Conflict Risk

A clear niche with distinct, repo-specific triggers — bloomwifi.today, the specific spreadsheet, ./update-passwords — leaving minimal overlap risk with other skills; even the generic-sounding "deploy" trigger is pinned to the named site.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

x-n2o/bloomwifi.github.io

Path

.claude/skills/wifi-password-update/SKILL.md

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.