Run any Skill in Manus with one click

gitbook-redirects

Stars23

Forks103

UpdatedJuly 6, 2026 at 14:43

Build a GitBook redirect CSV when mariadb-docs pages are renamed, moved, split, or retired. Use when the user asks to "create a redirects CSV", "make GitBook redirects", "set up redirects for moved/retired pages", or when a page-restructuring task removes or relocates published URLs. Produces the CSV; a GitBook site admin imports it manually (no API/MCP).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mariadb-corporation

mariadb-corporation/mariadb-docs

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	gitbook-redirects
description	Build a GitBook redirect CSV when mariadb-docs pages are renamed, moved, split, or retired. Use when the user asks to "create a redirects CSV", "make GitBook redirects", "set up redirects for moved/retired pages", or when a page-restructuring task removes or relocates published URLs. Produces the CSV; a GitBook site admin imports it manually (no API/MCP).
allowed-tools	Bash, Read, Grep, Glob, Write
owners	["shinz"]
last_verified	"2026-07-06T00:00:00.000Z"
status	active

gitbook-redirects

Produce a GitBook redirect CSV so old URLs don't dead-end after pages are renamed, moved, split, or retired. mariadb-docs has no in-repo redirect mechanism; GitBook redirects are configured manually in the site UI (no API/MCP), so this skill's deliverable is the CSV — a GitBook site admin imports it.

Full reference (read it): dev-docs/cookbook-gitbook-redirects.md. This skill is the procedure; the cookbook is the canonical explanation.

When to use

The user says: "create a redirects CSV", "make GitBook redirects", "redirect the old URLs", "set up redirects for the pages we moved/retired". Also run it as a follow-up whenever a task (often a DOCS-XXXX consolidation, split, or rename) removes or relocates published URLs — in addition to repointing in-repo inbound links (lychee only catches in-repo breakage).

Procedure

Gather the old → new pairs. From the task, the PR diff, or the user: every retired/moved page (its old path) and where it now lives (the surviving canonical page). Include retired section/landing pages too, pointed at the nearest surviving landing — not just leaf pages. For deletions, git log --diff-filter=D --name-only on the branch lists what was removed.
Derive each path:
- old URL → source: a site-relative path with leading slash, including the space prefix, .md dropped, README.md → its directory. Server space = /server/....
- new page → destination: a full absolute URL — https://mariadb.com/docs/server/<path>.
- Watch slug quirks: the on-disk basename is the slug (suffixes like -1 carry through).
Verify the base once. Open one real canonical page in a browser (or confirm with the user) that its live URL matches the https://mariadb.com/docs/server/... you generated. If the host/base differs, it's a find-and-replace on the prefix.
Write the CSV to a working file outside the repo (e.g. the scratchpad — it is not committed):
- Header exactly source,destination.
- One row per retired page + section landing.
Hand it off. Tell the user to import it in GitBook → the site → Settings → Redirects (single redirect or CSV import). Note the two failure modes so they can self-diagnose: Invalid destination URL → a destination isn't a full URL; a header error → it isn't source,destination.

Output shape

source,destination
/server/server-usage/basics/mariadb-usage-guide-1,https://mariadb.com/docs/server/mariadb-quickstart-guides/mariadb-usage-guide

Guardrails

Do not commit the CSV to the repo, and do not attempt the import yourself — there is no Git/API/MCP path; it's a manual GitBook UI action by a site admin.
Still repoint in-repo inbound links to the retired pages separately (that's not what redirects cover).

More from this repository

same repository

mariadb-alter-user

mariadb-corporation/mariadb-docs

MariaDB-specific syntax and behavior for ALTER USER and SET PASSWORD — IF EXISTS warning-not-error semantics, IDENTIFIED BY vs IDENTIFIED BY PASSWORD vs IDENTIFIED VIA/WITH multi-plugin auth, PASSWORD EXPIRE variants and default_password_lifetime interaction, ACCOUNT LOCK/UNLOCK, resource limits, TLS/REQUIRE options, and SET PASSWORD's three literal forms (PASSWORD(), OLD_PASSWORD(), pre-hashed string — there is no cleartext-string form). Use when writing, generating, or reviewing statements that create/change account credentials, expire or lock accounts, or set passwords on MariaDB.

2026-07-2023

mariadb-create-user

mariadb-corporation/mariadb-docs

MariaDB-specific syntax and behavior for CREATE USER — multiple authentication methods chained with OR, IDENTIFIED BY / IDENTIFIED BY PASSWORD / IDENTIFIED VIA|WITH plugin USING|AS 'string'|PASSWORD(...), the default authentication plugin, REQUIRE TLS options, WITH resource-limit options, PASSWORD EXPIRE variants, ACCOUNT LOCK/UNLOCK, OR REPLACE, IF NOT EXISTS, and account-name/host defaulting. Covers CREATE USER only (not GRANT's implicit user-creation path). Use when writing, generating, or reviewing CREATE USER statements that target MariaDB.

2026-07-2023

mariadb-drop-user

mariadb-corporation/mariadb-docs

MariaDB-specific behavior for DROP USER and RENAME USER — multiple accounts per statement, IF EXISTS turning a missing-user error into a note, the active-connections warning (dropped users keep working until their session ends; new connections are blocked), no cascade onto objects owned or privileges granted by the dropped user, dangling DEFINER references left behind on views/routines/triggers, and RENAME USER preserving privileges across the rename with no active-session check. Use when writing, generating, or reviewing DROP USER or RENAME USER statements, or account-lifecycle cleanup scripts, that target MariaDB.

2026-07-2023

mariadb-grant

mariadb-corporation/mariadb-docs

MariaDB-specific GRANT behavior — privilege scope levels (global/db/table/column/routine), implicit account creation interacting with the NO_AUTO_CREATE_USER sql_mode (on by default), MariaDB-only privileges LLMs won't know (BINLOG MONITOR, DELETE HISTORY, SET USER, FEDERATED ADMIN, READ_ONLY ADMIN, etc.) and the SUPER-privilege split, GRANT PROXY, resource limits, REQUIRE TLS options, and MariaDB roles (GRANT role TO user/role, WITH ADMIN OPTION, single-active-role semantics). Use when writing, generating, or reviewing GRANT statements or privilege/role designs that target MariaDB.

2026-07-2023

mariadb-revoke

mariadb-corporation/mariadb-docs

MariaDB-specific syntax and behavior for REVOKE — the mirrored five-form grammar (privilege ON object, the special ALL PRIVILEGES/GRANT OPTION form with no ON clause, PROXY, role revocation, ADMIN OPTION FOR role), the USAGE-privilege gotcha, ER_NONEXISTING_GRANT on mismatched revoke level, and the absence of an IF EXISTS clause. Use when writing, generating, or reviewing REVOKE statements (privileges, roles, or proxy) against MariaDB.

2026-07-2023

mariadb-control-flow-functions

mariadb-corporation/mariadb-docs

MariaDB control-flow functions and operators — IF(), IFNULL()/NVL(), NULLIF(), COALESCE(), the CASE operator (simple and searched forms), NVL2(), and DECODE/DECODE_ORACLE. Use when writing SQL that branches on a condition, substitutes for NULL, or matches a value against a list of alternatives in MariaDB.

2026-07-2023

name	gitbook-redirects
description	Build a GitBook redirect CSV when mariadb-docs pages are renamed, moved, split, or retired. Use when the user asks to "create a redirects CSV", "make GitBook redirects", "set up redirects for moved/retired pages", or when a page-restructuring task removes or relocates published URLs. Produces the CSV; a GitBook site admin imports it manually (no API/MCP).
allowed-tools	Bash, Read, Grep, Glob, Write
owners	["shinz"]
last_verified	"2026-07-06T00:00:00.000Z"
status	active

gitbook-redirects

Full reference (read it): dev-docs/cookbook-gitbook-redirects.md. This skill is the procedure; the cookbook is the canonical explanation.

When to use

Procedure

Gather the old → new pairs. From the task, the PR diff, or the user: every retired/moved page (its old path) and where it now lives (the surviving canonical page). Include retired section/landing pages too, pointed at the nearest surviving landing — not just leaf pages. For deletions, git log --diff-filter=D --name-only on the branch lists what was removed.
Derive each path:
- old URL → source: a site-relative path with leading slash, including the space prefix, .md dropped, README.md → its directory. Server space = /server/....
- new page → destination: a full absolute URL — https://mariadb.com/docs/server/<path>.
- Watch slug quirks: the on-disk basename is the slug (suffixes like -1 carry through).
Verify the base once. Open one real canonical page in a browser (or confirm with the user) that its live URL matches the https://mariadb.com/docs/server/... you generated. If the host/base differs, it's a find-and-replace on the prefix.
Write the CSV to a working file outside the repo (e.g. the scratchpad — it is not committed):
- Header exactly source,destination.
- One row per retired page + section landing.
Hand it off. Tell the user to import it in GitBook → the site → Settings → Redirects (single redirect or CSV import). Note the two failure modes so they can self-diagnose: Invalid destination URL → a destination isn't a full URL; a header error → it isn't source,destination.

Output shape

source,destination
/server/server-usage/basics/mariadb-usage-guide-1,https://mariadb.com/docs/server/mariadb-quickstart-guides/mariadb-usage-guide

Guardrails

Do not commit the CSV to the repo, and do not attempt the import yourself — there is no Git/API/MCP path; it's a manual GitBook UI action by a site admin.
Still repoint in-repo inbound links to the retired pages separately (that's not what redirects cover).