Generate SEO Slug

seo.generate_slug

ProductionBounded custom (Class B)Deterministicstrictinstantv1.0.0

No network

Overview

Turn a title into one ASCII path segment with an explicit separator and length policy We never open a connection, resolve DNS, or follow a redirect. The answer is a structured fact or policy result you can store. A successful call costs 1 execution credit.

Slug rules look simple until accents and length caps disagree; one contract owns the transform.

Reliability

seo.generate_slug is stable for identical input. Identical input always produces identical JSON. SEO_INPUT_REQUIRED means a required field is missing or has the wrong shape, so send the published object rather than a guessed map; retrying unchanged will not help. SEO_INPUT_TOO_LARGE means a value exceeds its ceiling, so trim it. SEO_HTML_MALFORMED means the HTML could not be parsed under the offline HTML contract, so fix the markup. SEO_XML_MALFORMED means the XML is not well-formed, so correct it. SEO_XML_DOCTYPE_NOT_ALLOWED means the XML includes a DOCTYPE declaration, so strip the DOCTYPE and resend; we refuse DTDs rather than expanding entities. SEO_JSONLD_MALFORMED means a JSON-LD block is not usable JSON, so correct it. SEO_PROFILE_UNKNOWN means the named profile is not bundled, so send one of the published profile ids. SEO_TOO_MANY_RECORDS means a list exceeded its ceiling, so split the batch. SEO_GRAPH_LIMIT_EXCEEDED means the graph exceeded its node or edge ceiling, so shrink it. SEO_INVALID_URL means a URL string is not a usable RFC 3986 URI, so send an absolute URI. SEO_OBSERVATION_INCOMPLETE means required observation coverage is missing, so add the missing evidence. SEO_INPUT_CONFLICT means two fields that cannot be used together were both supplied, so drop one. Retrying an unchanged request will not help.

Context footprint

Returns a compact structured record. A successful call costs 1 execution credit.

When to use it

When you already have a title or heading and need one ASCII path segment with a published separator and length cap.

When you want to check a slug a CMS already produced — use seo.validate_slug — or you still need to publish the page.

Scope

Note

Turn a title into one ASCII path segment with an explicit separator and length policy.

Non-goals

Does not fetch a URL, resolve DNS, or run a browser
Does not predict ranking, choose a winner, or claim live index status
Does not publish, redirect, or choose keywords

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

analysisparsing

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input8 KB

How we handle your data

Sensitive output possible

What this means

This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
This skill does not target sensitive data.
The response may contain submitted or transformed content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
text	string	Yes	Required. Title or label to turn into one path segment, up to 2048 UTF-8 bytes.
separator	string	No	Single character used between words. Omit it and we use a hyphen.
maxLength	integer	No	Maximum slug length after cleaning. Omit it and we use 80.
transliterate	boolean	No	When true, Latin diacritics fold to ASCII. Omit it and we transliterate.

Output schema

Field	Type	Required	Description
slug	string	Yes	Generated path segment, possibly empty when nothing survives cleaning.
profile	string	Yes	Effective slug profile id.
separator	string	Yes	Separator character actually used.
length	integer	Yes	Character length of slug.
sourceLength	integer	Yes	Character length of the original text.
truncated	boolean	Yes	True when the cleaned form exceeded maxLength.
transliterate	boolean	Yes	Whether diacritic folding was applied.
transformations	array	Yes	Named cleaning steps that actually ran, in order, such as lower_case, separator_fold, or truncate.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"seo.generate_slug","input":{"text":"Cafe resume 2026"}}'

Integrations

TypeScript SDK

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("seo.generate_slug", {"text":"Café résumé 2026"});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.
SEO_INPUT_REQUIRED	400	No	The request payload failed this skill's input validation.
SEO_INPUT_TOO_LARGE	429	No	A size, quota, rate, or time limit was exceeded.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not fetch a URL, resolve DNS, or run a browser
Does not predict ranking, choose a winner, or claim live index status
Does not publish, redirect, or choose keywords
Checking an existing CMS slug
Writing meta titles

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "seo.generate_slug",
  "input": {
    "text": "Café résumé 2026"
  }
}

Examples

Primary business path

Inputjson

{
  "text": "Café résumé 2026"
}

Expected outputjson

{
  "profile": "seo.slug.default@1",
  "transformations": [
    "lower",
    "transliterate",
    "separators"
  ],
  "slug": "cafe-resume-2026",
  "truncated": false,
  "sourceLength": 16,
  "separator": "-",
  "length": 16,
  "transliterate": true
}

Tip

First realistic scenario for this skill.

Boundary or option path