CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

spline-3d-integration

Use when adding interactive 3D scenes from Spline.design to web projects, including React embedding and runtime control API.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/spline-3d-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 SKILL.md body is a well-structured, reasonably lean overview with a clear workflow and concrete setup details, but it is fatally incomplete as a bundle: every guide and example file it routes to is missing, leaving the actual integration instructions (and all code) absent. Secondary issues are the irrelevant "Strict Rules" mandate section and the lack of any post-integration verification step.

Suggestions

Ship the referenced bundle files (guides/VANILLA_INTEGRATION.md, guides/REACT_INTEGRATION.md, guides/PERFORMANCE.md, guides/COMMON_PROBLEMS.md, and the three examples/ files) — or inline minimal quick-start embed snippets for the top stacks into SKILL.md so the skill works standalone. Without these, every reference is a dead link and the skill provides no executable integration code.

Delete the "Strict Rules" section: "ABSOLUTE MANDATE: Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX" is generic mandate-fluff that consumes tokens without adding integration guidance.

Add a final verification step to the workflow (e.g., confirm the scene renders, test the fallback for unsupported browsers/mobile, and check load performance against the PERFORMANCE.md guidance) so the sequence ends in a validation checkpoint.

DimensionReasoningScore

Conciseness

Mostly lean (stack→package table, terse Play Settings checklist, URL format block), but two sections pad it: "What Is Spline?" explains a concept Claude can be trusted to know or look up ("a browser-based 3D design tool — think Figma, but for 3D"), and the entire "Strict Rules" section is mandate-fluff ("ABSOLUTE MANDATE: Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX") unrelated to the integration task. Not 4 because the Strict Rules section is wholly unnecessary rather than a minor trim, and not 2 because the bulk is efficient tables and checklists.

3 / 5

Actionability

Setup guidance is genuinely concrete — exact package per stack ("@splinetool/react-spline/next", "@splinetool/runtime"), exact export path ("Export → Code Export → copy the prod.spline.design URL"), and specific toggles with rationale. But the executable core is entirely deferred: all code lives in guides/ and examples/ files that do not exist in the bundle, so there is no runnable embed snippet, no install command, and the "Production-ready lazy-loaded React wrapper" and other promised examples are dead links. This lands at "some concrete guidance but incomplete; missing key details" rather than 4.

3 / 5

Workflow Clarity

Clear three-step sequence (identify stack → get scene URL with a pre-copy checklist → read the relevant guide) with explicit checkpoints: "check the existing project files", the Play Settings checklist "Before copying the URL", and "Always read COMMON_PROBLEMS.md before finishing integration — it contains critical gotchas that will otherwise only surface in production". Not 5 because there is no post-integration validation/verification step (e.g., confirm the scene loads and the fallback renders); not 3 because the checkpoints that exist are explicit and well-placed, and the operation is non-destructive so the batch/destructive cap does not apply.

4 / 5

Progressive Disclosure

The body's structure is well-designed — Quick Reference and Working Examples tables that clearly signal one-level-deep references by task. However, scored against the actual bundle structure: none of the referenced files exist. guides/VANILLA_INTEGRATION.md, guides/REACT_INTEGRATION.md, guides/PERFORMANCE.md, guides/COMMON_PROBLEMS.md, and all three examples/ files are absent, and there are no references/, scripts/, or assets/ directories at all. Every navigation path in the skill is a dead link, so progressive disclosure fails in practice — the detailed materials the overview promises are simply missing. Not 1 because the SKILL.md itself is well-organized and references are clearly signaled, not buried or nested; not 3 because references that resolve to nothing do not function as progressive disclosure.

2 / 5

Total

12

/

20

Passed

Description

73%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 solid, appropriately concise description with an explicit trigger clause and a clearly named, highly distinctive domain. Its main weakness is that the "what" is compressed into the "when" clause and capability coverage stops at React plus runtime API, leaving the description narrower than the skill's actual scope.

DimensionReasoningScore

Specificity

"adding interactive 3D scenes from Spline.design to web projects, including React embedding and runtime control API" names the domain and roughly two concrete capabilities (React embedding, runtime control API), but coverage is not comprehensive — no mention of vanilla/web-component embedding, Vue/Next.js, events, or performance, which the body itself shows are part of the skill. Not 4 because it does not list several distinct specific actions, only one primary action with two supporting contexts.

3 / 5

Completeness

The "when" is explicit ("Use when adding interactive 3D scenes from Spline.design to web projects") and the "what" is present but compressed into the same clause (embedding scenes, React embedding, runtime control API). Not 5 because, unlike the anchor-5 pattern, there is no standalone what-statement and the when-clause offers only one trigger framing rather than concrete trigger variations (e.g., "when the user mentions Spline, .splinecode files, or embedding 3D scenes").

4 / 5

Trigger Term Quality

Good natural keywords: "interactive 3D scenes", "Spline.design", "web projects", "React embedding", "runtime control" — terms a user needing this skill would plausibly say. Not 5 because common variations are missing: "3D model", "embed 3D", ".splinecode", "spline viewer", or framework names users actually mention (Next.js, Vue).

4 / 5

Distinctiveness Conflict Risk

"Spline.design" names a specific tool, giving a clear niche with distinct triggers; "interactive 3D scenes" plus the product name makes conflict with generic web/3D skills (three.js, WebGL) minimal. Not 4 because the named proprietary tool is a stronger discriminator than the anchor-4 example's generic file formats.

5 / 5

Total

16

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 7 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/spline-3d-integration/SKILL.md

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.