portaljs-architect

Recommend a data-portal architecture (storage, compute, catalog, access, hosting, metadata) from stated needs, then hand off to the build skills. The advisory entry point. Use when starting a new data-portal project and the underlying architecture has not yet been decided.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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, lean advisory skill with a clear validated workflow and a real bundled reference. Its main weakness is reliance on an external GitHub-hosted command file as the 'single source of truth' for the decision tables, which slightly undercuts both inline actionability and self-contained progressive disclosure.

Suggestions

Bundle the decision tables (or at least the Storage/Catalog/Compute and Access/Hosting decision matrices) into references/reference.md so the skill is self-contained and actionable offline instead of pointing to an external GitHub URL for the core logic.

Tighten the three worked examples — Example 2 and Example 3 partly restate the default stack already covered in Instructions; condensing them to the distinct decision each illustrates would save tokens.

De-duplicate the DATA_QUERY / data-tier knob explanation so it lives authoritatively in one place (reference.md) and is only briefly referenced from Instructions and Examples.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no primers on what a data portal or DuckDB is), but the three worked examples are somewhat verbose and the DATA_QUERY/data-tier knob detail is restated across Instructions, Examples, and reference.md, leaving minor trim opportunities.	4 / 5
Actionability	Provides mostly executable guidance — concrete step sequence, named tools (du -sh, wc), the output file ./ARCHITECTURE.md, named follow-up slash-commands, and a perl -pi -e fix — but the core decision tables are delegated to an external GitHub-hosted command file rather than being fully actionable inline.	4 / 5
Workflow Clarity	A clear five-step sequence with an explicit validation checkpoint (Step 3 echoes the brief and waits for 'go' or corrections before Step 4 persists it), plus an Output section confirming the brief was echoed and confirmed; the skill is advisory/non-destructive so the destructive-cap does not apply.	5 / 5
Progressive Disclosure	Well-organized sections with a verified one-level-deep bundled reference (references/reference.md exists), but the primary executable workflow is delegated to an external GitHub URL rather than a bundled file, creating a navigation gap if the skill runs offline or the repo moves.	4 / 5
	Total	17 / 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 description: concrete actions, an explicit 'Use when' trigger, and a well-scoped niche that avoids conflict with related build skills. Trigger-term coverage is good but could add a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	Enumerates six concrete architecture slots ('storage, compute, catalog, access, hosting, metadata') and two concrete actions ('Recommend a data-portal architecture...then hand off to the build skills'), giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (recommend an architecture across six slots and hand off) and 'when' via the concrete trigger phrase 'Use when starting a new data-portal project and the underlying architecture has not yet been decided'.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('data-portal', 'new data-portal project', 'architecture', 'build skills') but is missing common synonyms and variations; the project-scaffolding domain has no file extensions to cover, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (pre-scaffold architecture advisory) with distinct triggers and explicitly states it 'does not build', minimizing overlap with the sibling build skills it hands off to.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: datopian/portaljs
Path: skills/portaljs-architect/SKILL.md
Commit: ebfd391

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.