CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pockethost-cli

PocketHost customer CLI (packages/cli, npm `pockethost`, formerly `phio`). Use when changing InstanceFileAccess, SFTP, deploy flows, or when validating that server changes still work with `pockethost dev/deploy` and SamKirkland FTP-Deploy-Action.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A high-quality project-orientation skill: it assumes Claude's competence, avoids concept explanations, and supplies concrete commands, file paths, and a compatibility checklist with validation checkpoints (smoke test, publish verification, key-mismatch recovery). The residual gaps are small — an undefined command used in the smoke test, a placeholder in the dev invocation, and inline detail that would fit better in reference files.

Suggestions

Define `pnpm dev:cli serve` (or point to where it's documented) before the smoke test uses it, and replace the literal `…` placeholder in `pnpm dev:cli-client -- …` with a concrete argument example.

Move the phio migration internals (envPaths path mapping, PKCS#8 migration, file-rewrite order) into a reference file under references/ and keep a two-line summary in SKILL.md, improving both conciseness and progressive disclosure.

Add a validation step for the `dev` watch flow (e.g., what a successful first sync looks like) so it matches the checkpoint quality of the deploy and publish workflows.

DimensionReasoningScore

Conciseness

The body is dense and factual throughout — command tables, env-var lists, port/auth specifics, include/exclude patterns — with essentially no explanation of concepts Claude already knows, and version-sensitive details (phio deprecation, PHIO_* vars) are correctly confined to migration/deprecation framing. It sits at 4 rather than 5 because sections like the migration path details (Linux-specific envPaths paths, PKCS#8 migration) carry inline detail that could be trimmed or split out.

4 / 5

Actionability

Guidance is largely executable: `pnpm dev:cli-client -- deploy <subdomain> -v`, `pnpm --filter pockethost build`, a copy-paste 3-step smoke test, and concrete publish verification ("install the packed tarball globally in a clean prefix **without `tsx` on PATH** and run `pockethost --version`"). Minor gaps keep it below 5: `pnpm dev:cli-client -- …` uses a literal `…` placeholder, and `pnpm dev:cli serve` appears in the smoke test without being introduced earlier.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with real checkpoints: the deploy-key flow is a numbered 1-3 list with error recovery (mismatch "throws with a link to `/account/keys`. Delete local key files to regenerate"), the smoke test ends in an explicit confirmation step, and publishing has a pre-flight validation. Not 5 because the `dev` (chokidar watch) flow lacks its own validation checkpoint — only `deploy` is smoke-tested.

4 / 5

Progressive Disclosure

Well-organized sections with tables and clear headers, and the one external pointer ("See [`.cursor/rules/pockethost-cli.mdc`](../../rules/pockethost-cli.mdc)") is clearly signaled and one level deep — though it points outside the skill bundle and no references/ directory exists. It is not 5 because detailed reference material (migration internals, deploy-key mechanics) is fully inlined in a >50-line body rather than split into bundle files.

4 / 5

Total

16

/

20

Passed

Description

87%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 project-scoped description: it precisely identifies the skill's subject with package and npm names, and provides an explicit, multi-trigger 'Use when' clause covering both change-side and validation-side use cases. The only meaningful gap is that it doesn't enumerate the full command surface (login, logs, sftp, migration), leaving trigger coverage slightly short of comprehensive.

DimensionReasoningScore

Specificity

Names several concrete, specific actions — "changing InstanceFileAccess, SFTP, deploy flows" and "validating that server changes still work with `pockethost dev/deploy` and SamKirkland FTP-Deploy-Action" — anchored to exact package and npm names. It falls short of 5 because coverage has gaps (auth/login, logs, instance linking, migration are not mentioned), but clearly exceeds 3's '1-2 concrete actions' bar.

4 / 5

Completeness

Explicitly answers both parts: the 'what' is unambiguous ("PocketHost customer CLI (packages/cli, npm `pockethost`, formerly `phio`)"), and the 'when' is a fully explicit trigger clause with concrete phrases ("Use when changing InstanceFileAccess, SFTP, deploy flows, or when validating that server changes still work..."). Not 4, since anchor 4 requires that the 'when' 'could be more explicit or specific', and here it is already specific and concrete.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "pockethost", "formerly `phio`" (includes the deprecated synonym), "SFTP", "deploy flows", "pockethost dev/deploy", "FTP-Deploy-Action" — terms a developer in this repo would actually say. Not 5 because common variations like "ftp", "login", "logs", or file tokens like `.pockethostconfig` are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: npm package names (`pockethost`, `phio`), a specific monorepo path, and named modules/actions (InstanceFileAccess, SamKirkland FTP-Deploy-Action) make it nearly impossible to trigger for the wrong skill. Voice is third person, so no specificity penalty applies.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

pockethost/pockethost

Path

.cursor/skills/pockethost-cli/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.