arcgis-starter-app

Scaffold ArcGIS Maps SDK applications with TypeScript and Vite. Includes both a minimal quick-start setup and a production-ready configuration with ESLint, Prettier, git hooks, and GitHub Actions CI/CD.

Quality

66%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./contexts/5.0/skills/arcgis-starter-app/SKILL.md

Quality

Discovery

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description with excellent specificity and distinctiveness, clearly naming the technology stack and both configuration tiers. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are naturally what a developer would search for.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to create a new ArcGIS Maps SDK project, set up a mapping application with Vite, or needs a GIS web app scaffold.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and configurations: scaffolding ArcGIS Maps SDK apps, TypeScript and Vite setup, minimal quick-start, production-ready config with ESLint, Prettier, git hooks, and GitHub Actions CI/CD.	3 / 3
Completeness	Clearly answers 'what does this do' (scaffold ArcGIS Maps SDK apps with specific tooling), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the description of capabilities.	2 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'ArcGIS', 'Maps SDK', 'TypeScript', 'Vite', 'ESLint', 'Prettier', 'git hooks', 'GitHub Actions', 'CI/CD', 'scaffold', 'quick-start', 'production-ready'. These are terms a developer would naturally use when requesting this kind of setup.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific combination of ArcGIS Maps SDK + TypeScript + Vite. This is a very clear niche that is unlikely to conflict with other skills like generic TypeScript scaffolding or general CI/CD setup skills.	3 / 3
	Total	11 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides highly actionable, copy-paste ready scaffolding for ArcGIS apps with excellent code completeness. However, it is severely bloated — full ESLint configs, CI/CD workflows, and editor configs consume most of the token budget and could be referenced as separate files or generated from brief instructions. The Common Pitfalls section with anti-pattern/correct pairs is useful but over-explains impacts that Claude can infer.

Suggestions

Move the full ESLint config, Prettier config, CI/CD workflows, editorconfig, and gitattributes into separate referenced files (e.g., 'See [PRODUCTION_CONFIG.md](PRODUCTION_CONFIG.md) for full ESLint, Prettier, and CI/CD configurations') to dramatically reduce token usage.

Trim the Common Pitfalls section to just the anti-pattern and fix — remove the 'Impact' paragraphs since Claude can infer why a missing API key or wrong moduleResolution causes problems.

Add explicit validation steps to the workflow, e.g., 'After `npm run dev`, verify the map renders at localhost:5173 — if you see a grey canvas, check the browser console for API key errors.'

Remove the Prerequisites section explaining what ArcGIS accounts are and what access tokens do — Claude knows this context. Keep only the actionable note about moduleResolution and CSS loading.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~600+ lines, with massive config file dumps (full ESLint config, Prettier config, CI/CD workflows, editorconfig, gitattributes) that Claude could generate from brief instructions. The Common Pitfalls section explains concepts Claude already knows (what happens when env vars are missing, how moduleResolution works). Much of this content is boilerplate that doesn't need to be spelled out line-by-line.	1 / 3
Actionability	Every file is provided as complete, copy-paste ready code with exact package versions, full configuration files, and working TypeScript examples. The quick start commands are concrete and executable.	3 / 3
Workflow Clarity	The skill provides two clear paths (minimal vs production) with project structures and quick start commands, but lacks explicit validation checkpoints. There's no step to verify the app actually loads correctly, no 'check that the map renders' step, and no error recovery guidance in the setup workflow itself.	2 / 3
Progressive Disclosure	The skill references related skills and samples at the end, which is good. However, the production setup section dumps hundreds of lines of config files inline (full ESLint config, CI/CD workflows, Prettier config) that should be in separate referenced files. The monolithic structure makes it hard to navigate.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (883 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: SaschaBrunnerCH/arcgis-maps-sdk-js-ai-context
Commit: d84407b

Reviewed: 1 day 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.