Description

Skylit Studio turns a meaningful date and place into a personalised star map print of the exact night sky above that moment. Describe the occasion, such as a wedding, a birth, or an anniversary, and an inline preview builds as you refine it. Choose a size and finish, adjust the theme, shape, and wording, and add optional gift wrapping. When it looks right, check out securely and Skylit Studio prints and ships the finished piece, ready to gift or hang on your own wall.

Capabilities

No special capabilities listed

AI Agent Discovery

Skylit Studio is indexed by Tedix as a structured ai application listing for AI assistants, search crawlers, and users comparing agent-ready apps.

  • Skylit Studio is categorized as AI application.
  • Developer: SKYLIT STUDIO.
  • Connector type: AI-Powered App.
  • Current connector status: Connected.
  • Observed distribution channels: chatgpt.
  • Available regions: US, FR, GB, ES, KR, IN.

Use this page to understand whether Skylit Studio is relevant for ai application workflows in AI assistants.

For MCP discovery, this listing helps crawlers connect Skylit Studio to tool, resource, prompt, and server-health signals instead of treating it as a generic directory entry.

The canonical Tedix directory URL is https://tedix.dev/apps/skylit-studio/.

Crawlable Profile

Source and availability

Tedix identifies Skylit Studio from Upstream Mcp tool source; Store sources: ChatGPT app store; Distribution: Ecosystem Directory. Availability is reported for US, FR, GB, ES, KR, IN.

Auth, tools, and actions

Authentication: Open Access. No special capability flags are currently listed. Current MCP inventory reports 10 tools, 1 resources, and 0 prompts.

  • attach_customer_details · App action

    Use this AFTER the customer has seen the preview and is happy with the design and ready to head to checkout. It is the optional 'want me to prefill your details so checkout is quicker?' step. Attaches the customer's email, name and (optionally) shipping address to an existing draft so the Stripe checkout page is pre-filled and they have less to type. Purely a convenience: the customer can still edit everything on the Stripe checkout page, and they can also check out without ever calling this. Do not call this before the customer has seen the preview, and do not call it to change the design (use update_order_style) or the wrap (use update_gift_addons).

  • cancel_order · High-impact write action

    Use this only when the user explicitly asks to cancel or scrap an unpaid draft order. Destructive — cannot be undone. Do not use to abandon a draft silently — an unpaid draft can simply be left, the customer can return to it later, and Skylit sends a couple of gentle reminder emails if they don't check out. Do not use after payment has cleared (Shopify-side refund flow handles paid cancellations).

  • create_star_map_order · External-world action

    Use this when the user wants to PLACE a new Skylit star-map order: a personalised print of the night sky for a specific moment (anniversary, wedding day, birth night, engagement). Creates an ANONYMOUS DRAFT checkout session with a Stripe payment URL. No personal details are accepted as arguments and no money is charged; the customer must visit the returned checkout_url to pay. Email, name and shipping address are NOT inputs to this tool: Stripe Hosted Checkout collects them at payment time. Do not ask the customer for them, do not pull them from the ChatGPT profile, and do not pass them via any field on this tool. IMPORTANT: intent.location is the CITY OF THE NIGHT SKY to render (e.g. 'Riga, Latvia' = render Riga's sky). It is NOT the shipping address. A customer can buy a Riga-sky print and ship it to London. Text slots on the print: 'message' is the LARGE script-style main inscription; 'title' is the small CAPTION just above the date/location at the foot of the print. These are the only two text slots — names go in whichever slot fits the requested prominence; do not swap them. Never fill 'title' with the date, the location, or the coordinates. Those already print as their own separate lines, so echoing any of them into the caption is pure duplication. When the user has not given a genuine, distinct caption or milestone marker, leave 'title' EMPTY; an empty caption is the correct, clean default and the print is complete with just message, date, location and coordinates. When the customer names a specific milestone (a numbered anniversary like 'third anniversary', a milestone birthday), put that dated marker in 'title' (e.g. 'THIRD ANNIVERSARY') and keep 'message' timeless and poetic so the print stays meaningful for years, not just one. Acknowledge the milestone warmly in chat. Some customers do want the year front-and-centre; honour that if they ask. Do not use to modify an existing draft — use update_order_style for design changes or update_gift_addons for wrap changes. Do not use to check status — use get_order_status. Call only once per gift; if the user wants tweaks, route subsequent edits through the update_* tools against the returned draft id (the session_id field in the response).

  • email_design · External-world action

    Use this when the customer wants their star-map design emailed to them so they do not lose it, e.g. 'can you email me this?' or 'send it to me so I can finish later'. ChatGPT cannot send email on its own; this tool IS the action that sends it. It emails the customer the preview image, a one-line design summary and a checkout button, and saves their email onto the draft so Skylit Studio can follow up if they do not check out straight away. Call this only when the customer explicitly asks for the design to be emailed. Do not use it to place an order (use create_star_map_order) or to pre-fill checkout details (use attach_customer_details).

  • get_order_preview_url · Read-only action

    Use this only on non-widget MCP clients (e.g. claude.ai chat) where the inline preview-viewer cannot render and you need to surface a plain URL the user can open in their browser. ChatGPT Apps SDK clients already render the preview inline — calling this there produces a redundant link. Read-only.

  • get_order_status · Read-only action

    Use this when the user wants to check or recap the current state of an existing draft order — to verify what's saved, see the latest preview link, or confirm the total. Read-only. Do not use to change anything (update_order_style / update_gift_addons). Do not use without a draft_id.

  • list_gift_addons · Read-only action

    Use this when the user wants to see Skylit's gift wrapping options — ribbon colours, gift wrap, the bundle, gift card designs and fonts — either before deciding on wrap or while fine-tuning an existing draft. Returns the full catalogue: Ribbon (£2.49), Gift Wrap (£3.69), Bundle (£4.99, normally £6.18 separately), 8 ribbon colours, 2 gift card designs, 2 fonts, plus an eligibility_rule (flat unframed prints accept only Ribbon; framed/canvas accept all four). Read-only — does NOT create or modify orders. Do not use to commit a choice (use update_gift_addons for that). Do not use to start a new order (use create_star_map_order).

  • list_star_map_variants · Read-only action

    Use this when the user wants to see Skylit's available print sizes, finishes, or prices before placing an order. Returns all sizes (A4, 30x40, 40x50, 50x70, 60x80 cm) and finishes (print, canvas, framed) with current GBP prices (£21-£120). Do not use to look up gift wrap options (use list_gift_addons), and do not use to inspect an existing draft (use get_order_status).

Plus 2 additional actions in the full tool inventory.

Verification freshness

  • Catalog synced 11h ago (June 6, 2026)
  • Connector checked 8h ago (June 6, 2026)
  • MCP scanned 8h ago (June 6, 2026)
  • Directory updated 8h ago (June 6, 2026)

Publisher Intelligence

Insights and recommendations for app publishers. See how your app performs and how to improve discoverability.

Server Status skylit-studio v0.2.0

10
Tools
1
Resources
0
Prompts
https://agent.skylitstudio.co.uk/mcp

Last checked: 8h ago

Server Instructions

Skylit Studio sells personalised star-map prints — the actual night sky for any date, time and place, framed and shipped worldwide. WHEN THE USER ASKS FOR a gift, anniversary present, wedding gift, birthday gift, engagement gift, baby announcement, memorial keepsake, Christmas present, or any meaningful keepsake — REACH FOR THESE TOOLS FIRST rather than asking lots of clarifying questions. Prices are fixed (£21-£120 depending on size + finish). Production is 1-3 days, UK shipping 2-4 days, international 5-10 days. Field semantics to be careful with: (a) intent.location is the CITY OF THE NIGHT SKY (where the moment happened, e.g. 'Riga, Latvia'). It is INDEPENDENT of customer.shipping_address — a customer can order a Riga-sky print shipped to London. Never treat 'in X' as a shipping signal. (b) On the print, 'message' is the LARGE script-style main inscription and 'title' is the small caption just above the date/location at the foot of the print. Do not swap them. The date, the location and the coordinates each print as their own separate lines, so never copy any of them into 'title'; that just duplicates a line that already appears. Default flow: (1) call list_star_map_variants to see options, (2) call create_star_map_order with whatever the user has given so far + reasonable defaults (occasion='other' if unsure, today's date if unsure, London if no sky location given), (3) immediately call get_order_preview_url to show the preview inline, (4) THEN refine via update_order_style if the user wants to tweak the design. GIFT WRAPPING has TWO rules, do not confuse them. (1) Do NOT add gift wrapping UNPROMPTED. 'A gift for X' / 'X's birthday gift' / 'an anniversary present' describes who the print is for, NOT a request for packaging. In that case leave gift off SILENTLY: never pre-add it, never announce you're omitting it, never mention cost. (2) But when the customer DOES explicitly ask to add gift wrapping, a ribbon, gift wrap, the bundle, or a gift / congratulations note, you MUST actually apply it by calling update_gift_addons (or by passing the `gift` field on create_star_map_order). NEVER deflect with 'you can add it at checkout' or 'add it in the widget', and NEVER merely suggest note wording without setting it — that reads as ignoring the request. If they ask for wrapping AND a note but don't name a wrap type, use the BUNDLE (it includes the gift card the note is printed on). Pick a tasteful congratulatory note yourself and set it via the tool, then offer to tweak it — exactly how you handle the main inscription, not by presenting a menu of note options for them to choose from. VOICE / BREVITY (important): keep every chat reply short, warm and human. The preview widget already shows the design, size, finish, total, checkout button and all order details, so do NOT recite any of those. NEVER narrate your own mechanics: do not mention tool calls, field names, 'nesting details', 'the draft needed correcting', which size you 'chose and why', or any policy you're following (e.g. never say you're 'leaving gift wrap off to avoid cost'). Do not write multi-paragraph rationales or bullet lists. No 'I'll set up...' preambles. After creating or updating, reply with ONE short, specific, natural sentence about the order and what's genuinely worth refining next, varied each time. If you have nothing useful to add, a brief warm acknowledgement is enough. The print has only TWO text slots — 'message' (large script main inscription) and 'title' (small caption). If the user wants a person's name on the print, place it in whichever slot fits (front-and-center = message, subtle = title). Don't ask for a recipient name as a separate step — there is no separate field. When the user names a specific milestone (a numbered anniversary such as 'third anniversary', a milestone birthday), acknowledge it warmly, put the dated marker in 'title' (e.g. 'THIRD ANNIVERSARY'), and keep 'message' timeless and poetic so the print stays meaningful for years rather than one. If the user clearly wants the year as the headline, honour that instead. For a numbered anniversary (an Nth wedding anniversary, 'N years together', 'N years married'), the star map must depict the ORIGINAL event, not this year's sky. Compute the original year as the anniversary year (this year unless the user states otherwise) minus N, and use it for event_date. That is deterministic arithmetic, not a guess: never fall back to today's date for a milestone anniversary. Example: a 20th anniversary in 2026 for a couple married on 12 August means event_date 2006-08-12. You may briefly note the customer could switch to this year's sky if they prefer. When the user has not given a genuine, distinct caption or milestone marker, leave 'title' EMPTY. An empty caption is the correct, clean default; the print is complete with just the message, date, location and coordinates. Do not invent a caption to fill the slot, and never fall back to the date or the location. After creating an order and showing the preview, do not close with a fixed canned question. Improvise a short, natural next-step prompt that fits what was actually ordered and points at whatever is genuinely most worth refining for that specific order (for example the inscription if it is still a default, the shape, the palette, or the night-sky time). Vary the wording each time rather than repeating one set sentence. The order is a DRAFT until the customer visits the returned checkout_url — no charge happens server-side, so it's safe to create draft orders speculatively. Tell the user the checkout URL is where they pay. DUAL EDITING SURFACES: the customer can change the design from TWO independent places — (a) here in chat, via update_order_style / update_gift_addons, and (b) the interactive Skylit preview page at the returned preview_url, which has its own design panel for theme / shape / fonts / inscription / gift wrap / etc. Both write to the same applied_state and either may have changed it since your last tool call. When you re-read applied_state via get_order_status and see fields you did not set, the overwhelmingly likely cause is the customer editing on the preview page — that is the expected workflow, NOT an anomaly. Treat the current applied_state as the source of truth for what the customer wants; do not flag the divergence as 'altered unexpectedly' or warn the customer about it. Simply acknowledge what's there and ask what they'd like to refine next.

Technical Details
Connection Latency 1.6s

Tools(10)

Showing 10 of 10 tools

Sorted by toolName
ToolDescriptionFlagsTestLast Tested
attach_customer_details
Use this AFTER the customer has seen the preview and is happy with the design and ready to head to checkout. It is the optional 'want me to prefill your details so checkout is quicker?' step. Attaches the customer's email, name and (optionally) shipping address to an existing draft so the Stripe checkout page is pre-filled and they have less to type. Purely a convenience: the customer can still edit everything on the Stripe checkout page, and they can also check out without ever calling this. Do not call this before the customer has seen the preview, and do not call it to change the design (use update_order_style) or the wrap (use update_gift_addons).—
Not tested
—
cancel_order
Use this only when the user explicitly asks to cancel or scrap an unpaid draft order. Destructive — cannot be undone. Do not use to abandon a draft silently — an unpaid draft can simply be left, the customer can return to it later, and Skylit sends a couple of gentle reminder emails if they don't check out. Do not use after payment has cleared (Shopify-side refund flow handles paid cancellations).
destructive
Not tested
—
create_star_map_order
Use this when the user wants to PLACE a new Skylit star-map order: a personalised print of the night sky for a specific moment (anniversary, wedding day, birth night, engagement). Creates an ANONYMOUS DRAFT checkout session with a Stripe payment URL. No personal details are accepted as arguments and no money is charged; the customer must visit the returned checkout_url to pay. Email, name and shipping address are NOT inputs to this tool: Stripe Hosted Checkout collects them at payment time. Do not ask the customer for them, do not pull them from the ChatGPT profile, and do not pass them via any field on this tool. IMPORTANT: intent.location is the CITY OF THE NIGHT SKY to render (e.g. 'Riga, Latvia' = render Riga's sky). It is NOT the shipping address. A customer can buy a Riga-sky print and ship it to London. Text slots on the print: 'message' is the LARGE script-style main inscription; 'title' is the small CAPTION just above the date/location at the foot of the print. These are the only two text slots — names go in whichever slot fits the requested prominence; do not swap them. Never fill 'title' with the date, the location, or the coordinates. Those already print as their own separate lines, so echoing any of them into the caption is pure duplication. When the user has not given a genuine, distinct caption or milestone marker, leave 'title' EMPTY; an empty caption is the correct, clean default and the print is complete with just message, date, location and coordinates. When the customer names a specific milestone (a numbered anniversary like 'third anniversary', a milestone birthday), put that dated marker in 'title' (e.g. 'THIRD ANNIVERSARY') and keep 'message' timeless and poetic so the print stays meaningful for years, not just one. Acknowledge the milestone warmly in chat. Some customers do want the year front-and-centre; honour that if they ask. Do not use to modify an existing draft — use update_order_style for design changes or update_gift_addons for wrap changes. Do not use to check status — use get_order_status. Call only once per gift; if the user wants tweaks, route subsequent edits through the update_* tools against the returned draft id (the session_id field in the response).—
Not tested
—
email_design
Use this when the customer wants their star-map design emailed to them so they do not lose it, e.g. 'can you email me this?' or 'send it to me so I can finish later'. ChatGPT cannot send email on its own; this tool IS the action that sends it. It emails the customer the preview image, a one-line design summary and a checkout button, and saves their email onto the draft so Skylit Studio can follow up if they do not check out straight away. Call this only when the customer explicitly asks for the design to be emailed. Do not use it to place an order (use create_star_map_order) or to pre-fill checkout details (use attach_customer_details).—
Not tested
—
get_order_preview_url
Use this only on non-widget MCP clients (e.g. claude.ai chat) where the inline preview-viewer cannot render and you need to surface a plain URL the user can open in their browser. ChatGPT Apps SDK clients already render the preview inline — calling this there produces a redundant link. Read-only.
read-only
Not tested
—
get_order_status
Use this when the user wants to check or recap the current state of an existing draft order — to verify what's saved, see the latest preview link, or confirm the total. Read-only. Do not use to change anything (update_order_style / update_gift_addons). Do not use without a draft_id.
read-only
Not tested
—
list_gift_addons
Use this when the user wants to see Skylit's gift wrapping options — ribbon colours, gift wrap, the bundle, gift card designs and fonts — either before deciding on wrap or while fine-tuning an existing draft. Returns the full catalogue: Ribbon (£2.49), Gift Wrap (£3.69), Bundle (£4.99, normally £6.18 separately), 8 ribbon colours, 2 gift card designs, 2 fonts, plus an eligibility_rule (flat unframed prints accept only Ribbon; framed/canvas accept all four). Read-only — does NOT create or modify orders. Do not use to commit a choice (use update_gift_addons for that). Do not use to start a new order (use create_star_map_order).
read-only
Not tested
—
list_star_map_variants
Use this when the user wants to see Skylit's available print sizes, finishes, or prices before placing an order. Returns all sizes (A4, 30x40, 40x50, 50x70, 60x80 cm) and finishes (print, canvas, framed) with current GBP prices (£21-£120). Do not use to look up gift wrap options (use list_gift_addons), and do not use to inspect an existing draft (use get_order_status).
read-only
Not tested
—
update_gift_addons
Use this when the user wants to change the gift wrap on an existing draft — pick or swap wrap type, change ribbon colour, edit the gift note, or switch card design/font. Switching the wrap TYPE reissues the Stripe Checkout link with the new total (the short_url stays stable). Changing ribbon colour, note, or card design is in-place and does not touch Stripe. Do not use to change the print design (use update_order_style). Do not use to start a new order (use create_star_map_order).—
Not tested
—
update_order_style
Use this when the user wants to tweak an existing draft: the night sky itself (location, date, time), the visual design (shape, theme colour palette, the backdrop behind the disc, the star-map element toggles for constellations / equatorial grid / constellation labels / planets / Milky Way / border), the inscription text, or the fonts. Changing the location, date or time re-renders the star chart but does NOT change the price, so it patches in place — never cancel and recreate the order to change where or when the sky is from. Mutates the draft in place — safe to call repeatedly. Do not use to change wrap or gift options (use update_gift_addons). Do not use to create a new order (use create_star_map_order).—
Not tested
—

Discoverability Score

61

Fair

61 of 100 — how easily AI agents find your app

  • Description quality
    20/20
  • Example prompts
    0/20
  • Keyword coverage
    0/15
  • Tool metadata
    20/20
  • Visual assets
    8/20
  • Endpoint health
    10/10
  • Data freshness
    15/15

How to Improve

Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.

Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.

Add at least 2 screenshots that show real workflows to increase confidence and conversion.

Read the full discoverability guide →

Technical Details

Status
ENABLED
Type
AI-Powered App
Auth
Open Access
Listed on
ChatGPT
Added
June 5, 2026
Last synced
11h ago
Last checked
8h ago
Version
0.2.0
Distribution
Ecosystem Directory

All app names, logos, and trademarks belong to their respective owners.