---
name: crafthinkera
description: Request custom physical products, parts, prototypes and objects through CrafThinkERA. Use when an agent needs a real object made from an intent, image, drawing or 3D file.
version: 0.2.0
---

# Make what agents want

## Objective
Move from a digital need to a delivered physical product without requiring a human to operate the ordering interface. This is the end-to-end product vision. Current tools support request intake and digital project work; autonomous quoting, payment, capacity reservation and machine dispatch are not available.

## Discover and load
- Read this skill into your agent's skill context. If your host supports local skills, save it as crafthinkera/SKILL.md in that host's skill directory. Installation paths depend on the host; fetching a file alone does not install an MCP connection.
- Specification: https://www.crafthinkera.com/llms.txt
- MCP discovery: https://www.crafthinkera.com/.well-known/mcp.json
- Connect a Streamable HTTP MCP client to https://www.crafthinkera.com/api/mcp
- Supply Authorization: Bearer <ctk_key> from your approved credential store. Never include the token in prompts, project text or logs.
- Discovery files do not auto-install a connection or register this service in an LLM catalog. The host must explicitly configure the endpoint and credential. Pilot keys are not OAuth sign-in.
- Initialize the MCP session, then call tools/list. Use the returned schemas as the source of truth.
- The repository stdio bridge @crafthinkera/mcp is not published to npm. Use remote HTTP; do not assume an npx registry install exists.

## Inputs
Collect purpose, quantity, dimensions in mm, material, finish, delivery region and deadline. Include tolerances, reference links and file references when available. Mark unknown values explicitly. Do not invent dimensions or treat a render as a verified manufacturable model.

## Execute within delegated authority
1. With project:create, call start_project with intent (8–4000 characters), locale (en or tr), and optional title. Save projectId.
2. Call inspect_project to read artifacts, work items and blocking questions.
3. With work:run, use work_on_project according to its discovered schema to interpret, answer questions or run an eligible digital step. Only answer from known requirements; ask the requester about unresolved design decisions.
4. Call prepare_execution to inspect step readiness without starting work. Paid steps require additional authorization and sufficient budget.
5. Call get_project to verify persisted state. Report actual stage, blockers and artifact references.
6. With quote:request, use request_quote with specification and idempotencyKey; inspect the runtime input schema. Operators set prices. Use get_quotes (quote:read) and prepare_production_order (order:prepare) to obtain the human approval path. An agent cannot approve or charge through these tools.
7. After the owner approves the exact quote/spec revision and pays through hosted PayTR, use get_production_job (production:read). Only a verified server payment event creates the job. Stop at unsupported capacity reservation or physical dispatch. AWAITING_MAKER is not a printed object or shipment.

## No-key request intake
If no MCP key exists, an authorized agent may POST https://www.crafthinkera.com/api/make-waitlist with Content-Type: application/json.

Required payload: email, brief (12–1500 characters), consent: true, locale: en|tr, role: DEVELOPER. Optional: name, sourceProductSlug, preferredMakerSlug, idempotencyKey. Leave website empty.

Use a real authorized contact and existing consent; do not fabricate either. Reuse a stable idempotencyKey for retries of the same request. A successful response stores a lead for review, not a paid order. Request MCP pilot access in the brief if tracked project tools are needed. Do not automatically submit a duplicate lead after an ambiguous response.

## Completion contract
Return: request or project reference when provided, observed status, outstanding questions, and next supported action. A person currently reviews and starts physical production; the requesting agent can originate and manage the digital request itself.