CtrlK
BlogDocsLog inGet started
Tessl Logo

ac-feature-analyzer

Analyze features and their dependencies. Use when mapping feature relationships, detecting blockers, optimizing build order, or identifying critical paths.

66

Quality

78%

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 ./.claude/skills/ac-feature-analyzer/SKILL.md

The canonical home for this skill is ac-feature-analyzer in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 clean, mostly executable overview that correctly pushes implementation detail into the bundled script. Its weaknesses are a generic descriptive workflow and slight redundancy between the Purpose/Analysis Types sections and the script's own capabilities.

Suggestions

Tighten the Workflow section from internal-stage labels into instructive steps with at least one validation checkpoint (e.g. confirm the dependency graph is acyclic before computing the critical path).

Drop or compress the Purpose and Analysis Types sections where they restate the frontmatter description and the script's own method list, redirecting to scripts/feature_analyzer.py instead.

Add brief copy-paste examples for the other public methods (get_next_feature, get_blocked_features, get_dependency_chain) alongside the existing analyze() quick start.

DimensionReasoningScore

Conciseness

Mostly efficient with executable quick-start code and tight bullet lists, but the Purpose section restates the frontmatter description and the Analysis Types bullets restate capabilities already implemented in the script — minor trimmable redundancy that keeps it below a 5.

4 / 5

Actionability

Quick Start gives concrete, executable Python referencing a real bundle file (scripts/feature_analyzer.py), but only the analyze() path is exemplified; the other public methods (get_next_feature, get_blocked_features, get_dependency_chain) are not shown, leaving minor gaps.

4 / 5

Workflow Clarity

A five-step sequence is present (Load, Graph, Analyze, Optimize, Report) but the steps are terse one-word labels that describe the analyzer's internals rather than instruct Claude, with no validation checkpoints or feedback loops; it sits at the 'sequence present, checkpoints missing' anchor.

3 / 5

Progressive Disclosure

The body is a well-organized overview with clear section headers and a well-signaled one-level-deep reference to the real scripts/feature_analyzer.py file, but the Analysis Types section inlines capability bullets that overlap with the script, a minor organization gap below a 5.

4 / 5

Total

15

/

20

Passed

Description

88%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 strong: it names concrete actions, gives an explicit 'Use when' trigger clause, and carves out a recognizable niche. The main gap is trigger-term breadth — a few natural synonyms would push trigger_term_quality and distinctiveness to full marks.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'mapping feature relationships', 'detecting blockers', 'optimizing build order', 'identifying critical paths' — with comprehensive coverage of the feature-analysis domain, matching the score-5 anchor rather than the 'minor gaps' of a 4.

5 / 5

Completeness

Clearly states what ('Analyze features and their dependencies') and explicitly answers when with concrete trigger phrases ('Use when mapping feature relationships, detecting blockers, optimizing build order, or identifying critical paths'), matching the score-5 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('features', 'dependencies', 'blockers', 'build order', 'critical paths'), but missing common synonyms a user might say like 'dependency graph', 'build sequence', or 'what to build next', so it sits above the midpoint rather than at comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a fairly distinct niche (feature dependency / critical-path analysis), but the surrounding ac-* planning ecosystem (ac-state-tracker, ac-complexity-assessor) creates minor overlap risk, placing it just below the 'minimal conflict risk' of a 5.

4 / 5

Total

18

/

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
fernandezbaptiste/Skrillz
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.