The body is lean: terse bullet points, a layout table, and named tool calls with no conceptual padding (it does not explain what a dashboard or chart is). It is not a 2 despite a minor duplicated events-search tip in Steps 0 and 2, because the dominant character is tight and every section earns its place.

Provides concrete, executable guidance: exact tool names (Amplitude:search, query_dataset, create_dashboard), specific parameters (entityTypes: ['EVENT','CUSTOM_EVENT']), concrete row heights (375/500/625/750px), column widths, and chartMetas display configs. It is not a 2 because the guidance names exact tools and values rather than pseudocode.

Clear numbered sequence (Step 0 discovery through Step 5 context) with verification preconditions ('Prototype with query_dataset to verify data', 'Collect all chart IDs before creating dashboard', 'Save all charts... before building dashboard') and an error-recovery feedback loop in Common Issues. It is not a 2 because verification checkpoints are present, so the batch-operation cap does not apply.

The skill is self-contained in a single well-organized SKILL.md with clearly labeled sections (Instructions, Layout Guidelines, Best Practices, Common Issues) and no nested or broken references; no bundle files exist and none are needed. It is not a 2 because there is no content that would clearly benefit from being split into a separate file.

Lists multiple concrete actions such as 'Builds comprehensive Amplitude dashboards', 'organizing charts into logical sections', and 'assembling existing charts into a cohesive view', rather than vague language. It is not a 2 because the actions are concrete and plural, not just a named domain.

Explicitly answers both 'what' ('Builds comprehensive Amplitude dashboards... organizing charts into logical sections') and 'when' via an explicit 'Use when creating a complete dashboard from scratch or assembling existing charts' clause. It is not a 2 because the trigger guidance is explicit, not merely implied.

Uses natural phrasings a user would say ('creating a complete dashboard from scratch', 'assembling existing charts', 'cohesive view'), and the suggest_when field reinforces this with 'build a dashboard' / 'I need a dashboard for'. It is not a 2 because the core dashboard terms and assemble-charts variations are well covered.

Anchored to a clear niche (Amplitude dashboards) with distinct triggers around dashboard assembly, making it unlikely to fire for unrelated skills. It is not a 2 because the scope is specific rather than a generic document/file skill.