here-now

Publish sites to {slug}.here.now and store files in Drives.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/productivity/here-now/SKILL.md

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 body is a strong, executable reference: concrete commands throughout, a clear sequenced auth workflow, honest scope-setting (what is live vs. what needs current docs), and bundle scripts that match the referenced paths. Its weaknesses are repetition of the docs URL and the duplicated API-key storage command, plus inline detail (option table, drive-share protocol) that would be better split into a reference file.

Suggestions

Deduplicate the docs URL (stated three times) and the API-key storage command (stated twice) to reclaim tokens.

Move the publish.sh option table and the drive-share token protocol into a bundled references file, keeping SKILL.md as the overview.

Add one inline error-recovery note for the publish flow (e.g. what to do when finalize fails) instead of deferring all error handling to the live docs.

Dimension	Reasoning	Score
Conciseness	The body is imperative and code-forward with almost no explanation of concepts Claude already knows, matching 'efficient; minor instances of over-explanation that could be trimmed'. The docs URL appears three times (lines 30, 215, 217) and the API-key storage command is repeated verbatim (lines 123 and 155), which is redundant padding.	4 / 5
Actionability	Every workflow ships copy-paste-ready bash with concrete placeholders (e.g. 'bash "$PUBLISH" {file-or-dir} --client hermes'), complete curl calls with real JSON bodies for the auth flow, a real state.json example, and a full flag table for publish.sh. This matches 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The API key flow is a clear numbered 5-step sequence, and the publish flow states its sub-steps ('create/update -> upload files -> finalize. A site is not live until finalize succeeds') plus a defined feedback channel ('Read and follow publish_result.* lines from script stderr'). Not 5 because explicit error-recovery steps for a failed publish are deferred to the live docs rather than given inline, so a checkpoint is implied rather than fully specified.	4 / 5
Progressive Disclosure	Both bundle scripts (scripts/publish.sh, scripts/drive.sh) exist, are referenced correctly via ${HERMES_SKILL_DIR} paths one level deep, and advanced topics (domains, payments, forking, proxy routes) are clearly delegated to a single live docs URL. This is 'good structure; most content is appropriately placed' with a minor gap: the full publish.sh option table and Drive-token handoff detail could live in a bundled reference file instead of the main body.	4 / 5
	Total	17 / 20 Passed

Description

53%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 states a clear, concrete 'what' anchored to a distinct product domain, but it completely lacks a 'when to use' trigger clause and misses the natural vocabulary (deploy, host, share, upload) users would actually say. It reads as a terse product tagline rather than a triggering description.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to publish, deploy, host, or share a website or files online, or wants private cloud storage for agent files.'

Include natural trigger terms and synonyms users would say — publish, deploy, host, share a link, static site, upload — rather than only product-specific terms like 'Drives'.

Clarify 'Drives' in plain language (e.g. 'private cloud storage folders') so the second capability is understandable without product knowledge.

Dimension	Reasoning	Score
Specificity	"Publish sites to {slug}.here.now and store files in Drives" names the domain and two concrete actions (publishing sites, storing files), matching the anchor for 1-2 concrete actions that are not comprehensive. It omits update, sharing, and the anonymous/permanent distinction, so it does not reach the 'several specific actions' level.	3 / 5
Completeness	The 'what' is clear (publishes sites at {slug}.here.now, stores files in Drives), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not lower, because the 'what' is concrete rather than vague.	3 / 5
Trigger Term Quality	"Publish", "sites", "store files" are relevant keywords, but common natural phrasings users would say ("deploy", "host a website", "share a link", "static site", "upload files") are absent, and "Drives" is product jargon rather than a user term. This matches 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The specific domain "{slug}.here.now" and the product-specific "Drives" give it a clear niche with minimal conflict risk against generic file or web skills. Minor overlap remains with generic hosting/deployment or cloud-storage skills since the description does not tie triggers to the here.now product name.	4 / 5
	Total	13 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/productivity/here-now/SKILL.md
Commit: 68fa7e9

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.