CtrlK
BlogDocsLog inGet started
Tessl Logo

portfolio-governance

Govern a personal software and creative portfolio with explicit ownership, lifecycle status, and attention limits. Use when deciding where a new idea belongs, reviewing overlapping repositories, selecting one active experiment, maintaining a portfolio ledger, or archiving dormant work without applying startup traction metrics to personal tools.

72

Quality

89%

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

86%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 well-structured, concise governance skill with concrete rules and clear safety boundaries. Main improvement would be weaving explicit validation/approval checkpoints directly into the intake workflow steps.

Suggestions

Add an inline validation gate to the intake workflow (e.g., after 'Find the canonical owner', require confirming the owner is not already claimed by another lifecycle) to make checkpoints explicit within the numbered sequence.

Optionally include a brief worked example of classifying one item end-to-end to lift actionability from concrete rules to fully copy-paste-ready guidance.

Consider splitting the lifecycle taxonomy into a reference file if the list grows, to keep SKILL.md an overview.

DimensionReasoningScore

Conciseness

The body is lean and efficient: short tables, terse rules, and no padded explanations of concepts Claude already knows, so every token earns its place.

5 / 5

Actionability

It gives concrete, specific guidance — explicit lifecycle taxonomies, hard attention limits ('at most one core-reliability item'), and decision rules — but as an instruction-only governance skill some guidance is abstract decision criteria rather than copy-paste specifics.

4 / 5

Workflow Clarity

The 'Portfolio intake workflow' is a clearly sequenced 5-step process and the Safety boundaries section supplies approval/rollback checkpoints for destructive operations, though the numbered steps themselves lack inline validate-then-proceed gates.

4 / 5

Progressive Disclosure

With no bundle files needed, the skill is a self-contained, well-organized body with clear section headers and tables, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

92%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, specific description with explicit trigger guidance and a clear niche. It uses third-person imperative voice and avoids vague fluff, with only minor room to add synonymous trigger terms.

DimensionReasoningScore

Specificity

The description names the domain and lists multiple concrete actions — 'deciding where a new idea belongs', 'reviewing overlapping repositories', 'selecting one active experiment', 'maintaining a portfolio ledger', 'archiving dormant work' — giving comprehensive coverage rather than minor gaps.

5 / 5

Completeness

It explicitly answers both 'what' (govern a portfolio with ownership, lifecycle status, and attention limits) and 'when' via a concrete 'Use when...' clause enumerating specific trigger scenarios.

5 / 5

Trigger Term Quality

Natural phrases a user would say ('where a new idea belongs', 'overlapping repositories', 'active experiment', 'archiving dormant work') are present with good coverage, but a few common synonyms/shorthands are missing so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — personal portfolio governance with an explicit boundary against applying startup traction metrics — yielding distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pvnkmnk/AgenticSelfHostSkills
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.