CtrlK
BlogDocsLog inGet started
Tessl Logo

poly-pizza-api

Use this skill whenever an LLM agent needs to search, browse, or download 3D models from Poly Pizza (poly.pizza) using their REST API. Triggers on any task involving: finding free low-poly 3D models, searching the Poly Pizza catalogue, fetching model metadata or download URLs, retrieving popular models, or downloading .glb files from Poly Pizza. Use this skill proactively whenever the agent needs to obtain 3D assets programmatically, even if the user just says "find me a 3D model of X" without mentioning Poly Pizza by name.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A highly actionable, well-structured API skill with executable code and clear endpoint documentation. The main weaknesses are minor redundancy (repeated API-key source) and the lack of explicit validation checkpoints in the brief batch/quick-match patterns.

Suggestions

Remove the duplicated API-key source line in the Notes section since it is already covered in Authentication.

Add an explicit validation step to the 'Batch fetch for a scene' and 'Find best match' patterns (e.g., check for empty results or non-200 responses before proceeding).

Consider moving the full search response-shape example into a short reference block or noting it is illustrative, to keep the overview lighter.

DimensionReasoningScore

Conciseness

Mostly lean with executable code and tables, but has minor padding: the API-key source is stated twice (Authentication and Notes) and the Notes section reiterates framework compatibility that assumes little new knowledge. Not below midpoint, just trimmable.

4 / 5

Actionability

Provides copy-paste-ready Python, concrete endpoint URLs, a full response-shape example, and a complete fetch_model function with real error handling — fully executable across common cases.

5 / 5

Workflow Clarity

Sequences are clear (search → pick → download; pagination loop) and the main function includes validation (raise_for_status, empty-results check), but the brief 'Batch fetch' and 'Find best match' patterns lack explicit verification checkpoints, leaving minor gaps.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Auth, Endpoints, Downloading, Licenses, Pagination, Errors, Patterns) with no bundle files; content is appropriately inline for a 3-endpoint API, though the ~250-line single file with full response examples borders on what could be split out.

4 / 5

Total

17

/

20

Passed

Description

100%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, well-constructed description that concretely names the API's actions, gives comprehensive natural trigger terms, and explicitly covers both what and when. Voice is appropriately third-person with no first/second-person penalties.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'search, browse, or download 3D models', 'fetching model metadata or download URLs', 'retrieving popular models', 'downloading .glb files' — giving comprehensive coverage of the API's capabilities rather than vague language.

5 / 5

Completeness

Explicitly states what the skill does (search/browse/download via the Poly Pizza REST API) and when to use it ('Use this skill whenever...', 'Triggers on any task involving...', plus the 'find me a 3D model of X' example), satisfying both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Covers natural user phrasing ('find me a 3D model of X'), synonyms ('3D assets', 'low-poly 3D models'), the domain name ('Poly Pizza'), and the file extension ('.glb'), matching the comprehensive-synonym anchor.

5 / 5

Distinctiveness Conflict Risk

The Poly Pizza / low-poly 3D model niche is clearly specific with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jasonkneen/tiny-world-builder
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.