CtrlK
BlogDocsLog inGet started
Tessl Logo

project-health

Portfolio health dashboard and risk matrix analysis. Usage: /project-health <dashboard|risk> [options]

57

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/project-health/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is well-structured, concise, and actionable, with a clean input schema and concrete script references. Its only weakness is mild redundancy and script references by path rather than inline examples.

DimensionReasoningScore

Conciseness

The body is lean with sectioned usage, a compact input-format JSON, and examples; it assumes Claude's competence with only minor redundancy between the Usage and Examples blocks, fitting the "efficient with minor trimming possible" anchor.

4 / 5

Actionability

Concrete commands, a complete input JSON schema, and explicit script paths with argument signatures give mostly executable guidance, with the minor gap that the scripts are referenced by path rather than shown inline.

4 / 5

Workflow Clarity

The two-mode workflow (dashboard vs risk) with a data file and optional --format is clearly sequenced; no validation checkpoint is needed since the operations are read-only analysis, matching "clear sequence with minor gaps".

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and one-level-deep references to external scripts and a sibling SKILL.md, matching the simple-skill exception for clear, well-signaled structure.

5 / 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 is specific and clearly niched but stops short of an explicit "Use when..." trigger clause, capping completeness. Trigger term coverage is reasonable but lacks synonyms or file extensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing portfolio health, generating project dashboards, or analyzing risk matrices."

Broaden trigger terms with natural synonyms (e.g. "project oversight", "risk register", ".json data files") to improve trigger-term coverage.

Name a couple more concrete actions (e.g. "flags schedule/budget/scope overruns") to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Portfolio health dashboard and risk matrix analysis" names the domain plus two concrete outputs (dashboards, risk matrices), matching the anchor that names a domain with 1-2 concrete actions but is not comprehensive.

3 / 5

Completeness

The description gives a clear "what" but the only "when" guidance is the "Usage:" invocation syntax, not an explicit trigger clause; per the guidelines a missing "Use when..." clause caps completeness at 3.

3 / 5

Trigger Term Quality

"portfolio health dashboard" and "risk matrix" are relevant natural terms, but coverage lacks common synonyms or file extensions, fitting the anchor for some relevant keywords missing variations.

3 / 5

Distinctiveness Conflict Risk

The portfolio-health/project-oversight niche is mostly distinct with only minor overlap risk against related PM skills, matching the "mostly distinct" anchor.

4 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.