disabling-services_skill

This skill hides deprecated or unavailable services from the documentation listing while preserving the page for SEO and direct access.

Dockerfile

311

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill coollabsio/coolify-docs --skill disabling-services

SKILL.md5.0 KB

Overview

This skill hides a service from the public services listing while keeping its documentation page live for SEO, bookmarks, and historical reference. It is intended for deprecating services, marking temporary unavailability, or removing services from the catalog without deleting their docs. The technique preserves direct URLs and supports easy reinstatement later.

How this skill works

You mark the service entry in the services list with disabled: true so it no longer appears in the listing UI. Then add a warning callout at the top of the service markdown page to explain deprecation, removal, or temporary downtime. Redirects and the markdown file remain intact so search engines and bookmarked links continue to resolve.

When to use it

Service is deprecated and should not appear in the catalog
Service is temporarily unavailable or broken upstream
Service has been removed or replaced by another service
You want to preserve SEO value and bookmarked pages
You need a historical reference or migration instructions for users

Best practices

Do not delete the service markdown file — keep it for SEO and bookmarks
Add a clear warning callout at the top of the page explaining status and next steps
Set disabled: true on the service entry in docs/.vitepress/theme/components/Services/List.vue
Provide migration instructions or a link to the replacement service when applicable
Keep any existing redirects pointing to the page to avoid broken links

Example use cases

Deprecating a legacy service and pointing users to a new alternative
Temporarily hiding a service while fixing upstream compatibility issues
Removing a service from the catalog but keeping documentation for historical context
Communicating a permanent removal with migration instructions and links
Preserving search engine traffic and bookmarked URLs after removal

FAQ

Yes. Keeping the markdown file ensures the page remains accessible at its URL and can continue to be indexed by search engines.

How do I re-enable a service later?

Remove disabled: true (or set to false) in the List.vue entry and delete the warning callout from the service markdown. Update any messaging to reflect availability.

Should I delete redirects that pointed to the service?

No. Keep redirects in place so users following old links still reach the documentation page.