manage-ccv-projects

Definisjonen av cc-viewer IM sitt kjerneansvar: å hjelpe brukeren med å administrere ccv-prosjektene på denne serveren. Enten brukeren spør «hva kan du / hva kan du hjelpe meg med», eller «list opp/hvilke prosjekter finnes» «hvilke ccv er startet» «hvilke prosjekter kjører» «start prosjekt X for meg / åpne det / få det i gang» «gi meg en adresse jeg kan åpne på mobil/lokalnett», eller bare «hi / hello / hei / hallo» som en ren hilsen uten et konkret ønske — i alle disse tilfellene bør du bruke denne ferdigheten (ved en hilsen tar du selv initiativ til å presentere deg og fortelle brukeren hva du kan). Så lenge meldingen handler om å vise ccv-prosjekter, starte dem eller om en tilgangsadresse, eller bare er en hilsen og litt småprat, så gå denne veien først — dette er IM sitt egentlige arbeid, ikke gå utenom det for å improvisere på egen hånd.

Quality

81%

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

Quality

Content

71%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 highly actionable with concrete commands and explicit success/error contracts, and its per-capability workflows are clearly sequenced with validation via exit codes. Its main weaknesses are repetition that hurts conciseness and a referenced script bundle that is missing and not clearly signaled.

Suggestions

Ensure the referenced `scripts/ccv-projects.mjs` bundle actually ships with the skill, and surface it as a clearly signaled one-level-deep reference (e.g. a 'Bundled script' section with a path link).

De-duplicate the 'single address line, no chatter' rule so it is stated once authoritatively rather than repeated across sections.

Add an explicit re-probe/retry step for transient start failures to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and avoids explaining concepts Claude already knows, but it restates the same guidance multiple times (e.g. the single-address-line rule appears in three places) and includes some conversational padding that could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands (`node scripts/ccv-projects.mjs <list\|probe\|start> [dir]`), exact output formats (`navn ⇥ sti ⇥ sist brukt`), a concrete success example (`http://192.168.1.23:7008?token=ab12cd34ef`), and enumerated error cases.	5 / 5
Workflow Clarity	Each capability has a clear sequence with an explicit validation checkpoint (script exit code: success prints one address line; non-zero exit read stderr and explain), plus error-recovery guidance for common failures, but there is no explicit re-probe/retry feedback loop for transient start failures.	4 / 5
Progressive Disclosure	The body is well sectioned by capability, but the referenced bundle (`scripts/ccv-projects.mjs`) is not present in the skill directory and the script reference is buried in prose rather than clearly signaled as a one-level-deep reference with a link, so navigation and structure are only partially realized.	3 / 5
	Total	15 / 20 Passed

Description

91%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 defines a specific niche and provides rich, natural trigger coverage including greetings. It is let down mainly by verbosity and conversational padding that dilutes the otherwise concrete capability list.

Suggestions

Tighten the description into a concise 'what' sentence plus a compact 'Use when...' trigger list to cut conversational padding.

Consider narrowing the bare-greeting trigger so it does not risk firing on every casual hello where no ccv context is present.

Dimension	Reasoning	Score
Specificity	Names the domain (ccv-prosjekter) and several concrete actions ("liste opp prosjektene", "starte et bestemt prosjekt", "overrekke brukeren en adresse"), but the actions are framed in conversational prose rather than a tight enumerated list, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what the skill does (administer ccv projects: list, start, provide access address) and when to use it, with concrete trigger phrases and an explicit Use-when-style clause ("i alle disse tilfellene bør du bruke denne ferdigheten").	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases a user would actually say, including "hva kan du", "list opp/hvilke prosjekter finnes", "start prosjekt X", "gi meg en adresse", plus greeting synonyms (hi/hello/hei/hallo).	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (ccv projects on this server) with distinct triggers and minimal overlap risk, though the bare-greeting trigger is broad enough to risk minor overlap with general assistant behavior.	4 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: weiesky/cc-viewer
Path: server/imSkills/no/manage-ccv-projects/SKILL.md
Commit: 817dc87

Reviewed: 9 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.