Name: placekey
Rating: 61.6 (1 reviews)
Author: membranedev

placekey

Placekey integration. Manage data, records, and automate workflows. Use when the user wants to interact with Placekey data.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/placekey/SKILL.md

Quality

Content

82%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 highly actionable with concrete, copy-paste CLI commands and a clear connection workflow including state-polling. The main gaps are a couple of trimmable explanatory lines and the absence of explicit validation feedback loops after running actions.

Suggestions

Trim the introductory 'Placekey is a universal identifier...' paragraph and 'Use action names and parameters as needed.' to tighten token budget.

Add a validation/check step after running actions or proxy requests, e.g. 'Check the output field and error code; retry on non-2xx with adjusted params.'

If the action reference grows, move the proxy flag table and detailed clientAction cases into a reference file and link to it from SKILL.md to better match the one-level-deep progressive disclosure pattern.

Dimension	Reasoning	Score
Conciseness	The body is efficient and command-driven with only minor over-explanation (the introductory 'Placekey is a universal identifier...' paragraph and the line 'Use action names and parameters as needed.'), fitting the anchor for efficient content with small trimmable bits.	4 / 5
Actionability	Provides copy-paste-ready CLI commands with flags and JSON examples covering connection setup, action search, action runs with JSON params, and proxy requests with a full options table, matching the anchor for fully executable guidance over common cases.	5 / 5
Workflow Clarity	The sequence (install, authenticate, connect, poll for READY, search, run) is clear with explicit connection-state polling, but there is no validation checkpoint after action runs or before relying on results, so it fits clear-sequence-with-minor-validation-gaps rather than full feedback loops.	4 / 5
Progressive Disclosure	The single SKILL.md file is organized into clear, well-signaled sections (install, auth, connecting, searching, running, proxy, best practices) with no nested references; with no bundle files present, structure relies on headers, which is good but not the ideal split-over-files pattern.	4 / 5
	Total	17 / 20 Passed

Description

62%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 cleanly answers what and when and is clearly anchored to Placekey, but the listed actions are generic and the trigger vocabulary is narrow. Tightening the action list to concrete Placekey operations and adding common synonyms would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Placekey operations such as 'convert addresses and coordinates to Placekeys, look up POIs, and join location datasets'.

Broaden the trigger phrase to natural synonyms, e.g. 'Use when the user mentions Placekeys, POI identifiers, location data, or joining datasets by place.'

Keep the explicit 'Use when...' clause but make the trigger conditions more specific to reduce ambiguity against generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Placekey) and lists a few action categories ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Placekey operations, matching the anchor for domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	States both what it does ('Placekey integration. Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Placekey data'); the 'when' is explicit but could be more specific, fitting the anchor where both are present with room for sharper triggers.	4 / 5
Trigger Term Quality	Includes 'Placekey' and 'Placekey data' as relevant keywords but misses common synonyms users might say (POI, location data, place identifiers), so coverage has gaps rather than being comprehensive.	3 / 5
Distinctiveness Conflict Risk	'Placekey integration' is a clear niche with the distinct trigger 'interact with Placekey data', giving minimal overlap risk with only minor broadness in 'manage data, records'.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/placekey/SKILL.md
Commit: f484c82

Reviewed: 5 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.