CtrlK
BlogDocsLog inGet started
Tessl Logo

arcgis-to-portaljs

Migrate a whole ArcGIS Hub site into a PortalJS Arc portal end-to-end. Harvests the Hub /data.json (DCAT-US) inventory, exports every FeatureService layer through the ArcGIS REST query API with resultOffset paging, converts each to the serverless dual tier (PMTiles render + GeoParquet query) with tabular items to Parquet, pushes everything to Cloudflare R2 via Git LFS, appends dual-tier datasets.json entries, and writes a source-vs-derived parity report. Use to move a City or sector ArcGIS Hub open-data portal onto PortalJS with no server-side compute.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 orchestrator skill body that delegates executable detail to clearly signaled one-level-deep references while keeping a concrete summary, error table, and examples inline. Inline copy-paste code and tighter instruction prose would lift the actionability and conciseness scores.

Suggestions

Inline one or two short, fully executable command snippets (e.g. the ogr2ogr/tippecanoe/duckdb conversion trio) so the body is copy-paste ready without opening references.

Tighten the 9-step Instructions summary by collapsing sub-clauses (e.g. namespace-mode and dedup rules) into the reference, keeping only the sequencing in the body.

Add an explicit validation gate callout (a bold 'Validate' step) between publish and the parity report to make the verification checkpoint as prominent as the rubric's anchor-5 example.

DimensionReasoningScore

Conciseness

Dense, competent prose that assumes Claude's knowledge and delegates detail to references, but the 9-step instruction summary is fairly long and could be marginally tightened.

4 / 5

Actionability

Provides concrete flags, API parameters, tool names, an error table, and three executable example invocations, though full copy-paste code blocks live in the referenced files rather than the body itself.

4 / 5

Workflow Clarity

Nine clearly sequenced steps with validation checkpoints (tool-check hard-stop, portal validation, parity report) and an error-handling table; the executable detail is delegated to references, leaving minor gaps.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to reference.md and sync-and-cutover.md (both present as real files), plus a labeled Resources section for easy navigation.

5 / 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, specific description that covers concrete actions comprehensively and includes an explicit 'Use to...' trigger clause. Minor room to add synonyms/file extensions for trigger terms.

DimensionReasoningScore

Specificity

Lists many concrete actions (harvests /data.json, exports FeatureService layers via REST query API with resultOffset paging, converts to PMTiles+GeoParquet, pushes to R2 via Git LFS, appends datasets.json, writes parity report) with comprehensive coverage.

5 / 5

Completeness

Clearly answers both 'what' (the detailed multi-step pipeline) and 'when' via the explicit trigger clause 'Use to move a City or sector ArcGIS Hub open-data portal onto PortalJS with no server-side compute.'

5 / 5

Trigger Term Quality

Good keyword coverage ('ArcGIS Hub', 'PortalJS', 'open-data portal', 'City or sector') but missing synonyms and file extensions that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (ArcGIS Hub to PortalJS migration) with distinct triggers and minimal overlap with the related portaljs-* skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.