CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fictiv

Operates Fictiv (app.fictiv.com), the on-demand manufacturing platform, end to end in the user's browser. Covers uploading CAD parts, configuring process, material, finish, threads, tolerances and inspections, getting instant or manual quotes, reading and fixing DFM feedback, choosing lead time and region, checking out and paying (card or PO), tracking orders, reordering, and troubleshooting. Applies when the user mentions Fictiv, wants a part CNC machined, 3D printed, sheet-metal fabricated, urethane cast, injection or compression molded, or die cast through an online service, asks to "get a quote" or "order parts" for a STEP/SLDPRT/STL file, wants to check a Fictiv quote or order status, or has a problem with a Fictiv upload, DFM warning, price or checkout. Also applies when the user wants custom parts manufactured and has a Fictiv account, even if Fictiv is not named.

77

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-engineered operational skill body: highly actionable with exact URLs, labels, commands, and DOM tactics, a clearly sequenced 10-step workflow with genuine validation checkpoints and an approval gate for money/legal actions, and clean progressive disclosure to verified one-level-deep references. The only weakness is mild verbosity in the intro's documentation-provenance commentary.

Suggestions

Trim the intro's provenance sentences ('The official sources reviewed on 2026-09-30 document... no public customer API, SDK, authentication, endpoint, or pagination contract' and 'Public-documentation review does not revalidate the September 2026 authenticated UI snapshot') to a single short caveat, keeping the no-API/verify-current-UI point without restating the review date twice.

The drawings-reconciliation bullet in step 5 is a dense four-line run-on; condensing it to two lines with the reconciliation edge cases moved to quoting.md would tighten the backbone while preserving the safety-critical points.

DimensionReasoningScore

Conciseness

The body is dense and operational with almost no explanation of concepts Claude already knows, but the intro carries provenance meta-commentary ('The official sources reviewed on 2026-09-30 document browser workflows and a managed cXML Punchout integration... no public customer API' and 'Public-documentation review does not revalidate the September 2026 authenticated UI snapshot') that partially duplicates the closing verify-before-acting caveat. This is efficient with minor trimming opportunities, matching anchor 4 rather than the every-token-earns-its-place level 5.

4 / 5

Actionability

Guidance is fully executable: a copy-paste-ready command ('python3 <skill-dir>/scripts/check_cad_file.py path/to/part.step [...] --process cnc'), exact URLs ('/pages/quotes/upload', '/pages/quotes/<quoteId>'), exact UI labels ('Request quote', 'Begin checkout', 'View feedback', 'Bulk configure parts', 'Move to...'), and DOM specifics ('hidden input[type=file]', 'check that the URL gains ?process=...', 'document.body.innerText' slicing anchors). All referenced scripts exist on disk with the described roles.

5 / 5

Workflow Clarity

The 10-step end-to-end workflow is clearly sequenced with explicit validation checkpoints: pre-flight before upload, polling quote_state.js until 'analyzing' is false plus verifying controls actually appeared, drawing/configuration reconciliation and a re-check after uploading a revised drawing, and a mandatory approval gate before 'Place order'. A task router routes edge cases to the right reference sections, and error-recovery paths (unrecognized layout, manual-quote splitting via 'Move to...') are given, matching the anchor-5 feedback-loop pattern.

5 / 5

Progressive Disclosure

The 'Files in this skill' table gives per-file 'Read it when' guidance, and every referenced path (6 reference files, 3 scripts) exists with one-level-deep structure; spot-checks confirm the numbered section references in the body (quoting.md sections 1, 9, 10; checkout-and-payment.md sections 2, 4-6; orders-library-teams.md sections 2-6; troubleshooting.md sections 2-4) resolve to real sections. The SKILL.md stays an overview/backbone with details appropriately split into references, matching anchor 5.

5 / 5

Total

19

/

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.

An exemplary description: it states what the skill does with a comprehensive, concrete action inventory and gives explicit 'applies when' triggers with natural user phrasing, process synonyms, and file extensions, all in third person and anchored to a specific platform. Distinctiveness is strong because nearly every trigger clause is Fictiv-gated.

DimensionReasoningScore

Specificity

The description lists ten-plus concrete actions ('uploading CAD parts, configuring process, material, finish, threads, tolerances and inspections, getting instant or manual quotes, reading and fixing DFM feedback, choosing lead time and region, checking out and paying (card or PO), tracking orders, reordering, and troubleshooting') covering the platform end to end. This matches the comprehensive-coverage anchor; it is not level 4 because there are no gaps in the action inventory.

5 / 5

Completeness

It explicitly answers both questions: 'what' ('Operates Fictiv... end to end in the user's browser', followed by a concrete capability inventory) and 'when' ('Applies when the user mentions Fictiv... asks to "get a quote" or "order parts"... or has a problem with a Fictiv upload, DFM warning, price or checkout', plus an unnamed-but-accounted case). This matches the anchor-5 example's structure.

5 / 5

Trigger Term Quality

It covers natural user phrasing comprehensively with synonyms and file extensions: 'get a quote', 'order parts', 'CNC machined', '3D printed', 'sheet-metal fabricated', 'urethane cast', 'injection or compression molded', 'die cast', 'DFM warning', 'order status', plus STEP/SLDPRT/STL. Consistent third-person voice ('Operates', 'Covers', 'Applies') throughout.

5 / 5

Distinctiveness Conflict Risk

Triggers are anchored to a named platform with its URL (app.fictiv.com), and every primary trigger names Fictiv or requires a Fictiv account, giving a clear niche with minimal conflict risk. The 'through an online service' clause is a deliberate extension of Fictiv's own process offerings rather than a generic trigger, so it does not drop to level 4.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

K-Dense-AI/scientific-agent-skills

Path

skills/fictiv/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.