CtrlK
BlogDocsLog inGet started
Tessl Logo

interactive-portfolio

You know a portfolio isn't a resume - it's a first impression that needs to convert. You balance creativity with usability. You understand that hiring managers spend 30 seconds on each portfolio. You make those 30 seconds count. You help people stand out without being gimmicky.

43

Quality

44%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/interactive-portfolio/SKILL.md

The canonical home for this skill is interactive-portfolio in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized catalog of portfolio design patterns with concrete, actionable tables and formulas, but it is undermined by a verbatim-repeated description paragraph, malformed code fences, and Sharp Edges references that resolve to sections that do not exist. These issues cost it clarity and navigability despite otherwise useful content.

Suggestions

Fix the code fences: the ```javascript blocks actually contain markdown/tables — either drop the language tag or convert them to plain fenced blocks so the markdown renders correctly.

Resolve the Sharp Edges table: either write the referenced sections (Right-Sizing, Mobile-First, Portfolio CTAs, Portfolio Freshness) or replace the dangling headers with the actual guidance inline.

Delete the verbatim repetition of the frontmatter description in the opening role paragraph; reference the skill's purpose once.

DimensionReasoningScore

Conciseness

The body is mostly efficient with useful tables and formulas, but the opening role paragraph repeats the frontmatter description verbatim and several section intros ('Structure that works for portfolios', 'How to present work effectively') restate the obvious, so it could be tightened.

3 / 5

Actionability

It gives concrete, usable artifacts — the 30-second test, essential-sections table, hero formula, project-card table, numbered case-study structure, and impact-rewrite table — which are actionable for an instruction-only skill, with only minor gaps.

4 / 5

Workflow Clarity

The skill is a patterns/reference catalog rather than a sequenced process; the case-study structure and 30-second test are ordered, but there are no checkpoints or validation steps, which fits a non-destructive advisory skill yet keeps it at the 'sequence present, checkpoints missing' anchor.

3 / 5

Progressive Disclosure

Content is a single file with clear section headers and no bundle files to split, but malformed code fences (e.g. ```javascript blocks containing markdown) and the Sharp Edges table pointing to non-existent sections ('## Right-Sizing Your Portfolio', '## Mobile-First Portfolio') break navigation.

3 / 5

Total

13

/

20

Passed

Description

31%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 a second-person, aspirational persona statement rather than a capability/trigger description: it conveys attitude about portfolio design but names no concrete actions and gives no 'when to use' guidance. It would not help Claude reliably decide when to load this skill.

Suggestions

Rewrite in third person with concrete verbs, e.g. 'Designs and structures interactive portfolio sites: hero sections, project showcases, and case studies.'

Add an explicit trigger clause: 'Use when building or redesigning a personal portfolio site, showcasing projects, or writing portfolio case studies.'

Replace aspirational filler ('make those 30 seconds count', 'stand out without being gimmicky') with the actual deliverables the skill produces.

DimensionReasoningScore

Specificity

The description names the domain (portfolio) but relies on abstract aspirational language ('balance creativity with usability', 'make those 30 seconds count', 'stand out without being gimmicky') with no concrete actions; the pervasive second-person voice ('You know', 'You balance') triggers the rubric's -1 specificity penalty, capping it at 1.

1 / 5

Completeness

It offers only a vague 'what' (helping people stand out) and provides no 'when' / 'Use when...' trigger clause, matching the 'vague what, no when' anchor; the missing trigger guidance also caps completeness per the rubric.

2 / 5

Trigger Term Quality

'portfolio' is a natural term a user would say and is the throughline, but common variations ('portfolio site', 'showcase work', 'case study') are absent, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

The portfolio niche is specific, but the aspirational framing and explicit overlap with `personal-branding` and `landing-page-design` (listed in Related Skills) leave real overlap risk with adjacent skills.

3 / 5

Total

9

/

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
administrakt0r/AI-Agents-Safe-Coding-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.