disabling-services
Hides documentation pages from search listings while keeping them live for existing bookmarks and SEO.
Install
mkdir -p .claude/skills/disabling-services && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4380" && unzip -o skill.zip -d .claude/skills/disabling-services && rm skill.zipInstalls to .claude/skills/disabling-services
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Hides or disables a service from the documentation listing while preserving the page for SEO and bookmarks. Use when deprecating services, marking services unavailable, setting disabled:true in frontmatter, or adding warning callouts to service pages. Keeps docs/services/ pages accessible via direct URL.Key capabilities
- →Mark services as deprecated or disabled
- →Add warning callouts to documentation
- →Filter services from documentation listings
- →Preserve direct URL access for SEO
- →Regenerate service data files
How it works
It updates frontmatter or adds specific warning patterns to markdown files, which are then detected by scripts to exclude the service from generated listings.
Inputs & outputs
When to use disabling-services
- →Deprecating documentation pages
- →Updating service status to disabled
- →Adding warning callouts to docs
About this skill
Disable Service Documentation
Keep the service page for existing deployments, search results, and bookmarks. Update its availability in content/docs/services/{slug}.mdx; do not delete it merely to hide a catalog entry.
Workflow
- Verify which service templates are unavailable and why. When only some deployment variants are disabled, describe that scope accurately rather than hiding an otherwise deployable service.
- Add the explicit frontmatter flag
disabled: truewhen the whole service should be hidden. - Add a visible MDX callout immediately after frontmatter, before the rest of the body. Explain the reason and, when known, link to verified updates, an advisory, or a replacement.
- Preserve any existing redirects in
nginx/redirects.conf. - Run
bun run generate:servicesand inspect both generated outputs. Include them with the page when committing.
---
title: "Service Name"
description: "Short service description."
category: "Utilities"
icon: "/docs/images/services/service-name-logo.svg"
disabled: true
---
<Callout type="warning" title="SERVICE TEMPORARILY DISABLED">
This service's one-click templates are temporarily unavailable in Coolify. Explain the verified reason and any action existing users need to take.
</Callout>
# Service Name

## What is Service Name?
Keep the existing service documentation here.
Use <Callout type="error"> for a security or removal warning when appropriate. Supported callout types and other examples are in CONTAINERS.md. Do not use VitePress ::: syntax.
How Availability Is Detected
scripts/services-data.mjs sets disabled: true if the frontmatter flag is true or the page contains one of these case-insensitive phrases:
SERVICE HIDDENSERVICE NOT AVAILABLESERVICE REMOVED FROM COOLIFYSERVICE TEMPORARILY DISABLED
Use the frontmatter flag even when the callout has a recognized title. A title such as SERVICE DEPRECATED alone does not trigger detection.
src/generated/services.json retains the service with disabled: true. src/components/data/services-list.tsx filters it out of the searchable catalog, and the directory generator omits it from content/docs/services/all.mdx. The page remains reachable at /docs/services/{slug}.
Verification
- The original
.mdxpage and its historical redirects still exist. - The callout states the verified reason, scope, and any action for existing deployments.
src/generated/services.jsoncontains the slug withdisabled: true.content/docs/services/all.mdxno longer links to the service.- At
http://localhost:3000/docs/services/overview, the service is absent; its direct page still loads and displays the warning.
See TESTING.md for isolated generator validation and CATALOG.md for the catalog contract. Neither generated file should be edited by hand.
Re-enable a Service
Once availability is verified, remove disabled: true and remove or retitle any notice matching the recognized phrases. Regenerate both catalogs and confirm that the service appears with the right category and logo. Keep any still-relevant guidance for existing deployments.
Related Skills
- adding-service-documentation: create or update a service page.
- renaming-services: change a service slug and preserve old URLs.
When not to use it
- →When the documentation file should be permanently deleted
Limitations
- →Requires running a build script to update the listings
- →Warning callout titles must match specific patterns for auto-detection
How it compares
This method maintains SEO and bookmark integrity by keeping the page live while signaling to the system that the service is inactive.
Compared to similar skills
disabling-services side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| disabling-services (this skill) | 1 | 6mo | Review | Beginner |
| schema-markup | 10 | 9mo | No flags | Intermediate |
| fixing-metadata | 1 | 9mo | No flags | Beginner |
| firecrawl-known-pitfalls | 0 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by coollabsio
View all by coollabsio →You might also like
schema-markup
davila7
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.
fixing-metadata
agentset-ai
Ship correct, complete metadata.
firecrawl-known-pitfalls
jeremylongshore
Identify and avoid FireCrawl anti-patterns and common integration mistakes. Use when reviewing FireCrawl code for issues, onboarding new developers, or auditing existing FireCrawl integrations for best practices violations. Trigger with phrases like "firecrawl mistakes", "firecrawl anti-patterns", "firecrawl pitfalls", "firecrawl what not to do", "firecrawl code review".
seo-review
leonardomso
Perform a focused SEO audit on JavaScript concept pages to maximize search visibility, featured snippet optimization, and ranking potential
concept-workflow
leonardomso
End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review
seo-structure-architect
sickn33
Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities. Creates search-friendly content organization. Use PROACTIVELY for content structuring.