platform-profiles
Platform-specific equivalents for GitLab and Bitbucket when generating repository documentation. Lookup tables for file paths, badges, Markdown rendering, CI/CD, and CLI tools. Load this skill when working on non-GitHub repos or generating cross-platform docs.
Best use case
platform-profiles is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Platform-specific equivalents for GitLab and Bitbucket when generating repository documentation. Lookup tables for file paths, badges, Markdown rendering, CI/CD, and CLI tools. Load this skill when working on non-GitHub repos or generating cross-platform docs.
Teams using platform-profiles should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/platform-profiles/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How platform-profiles Compares
| Feature / Agent | platform-profiles | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Platform-specific equivalents for GitLab and Bitbucket when generating repository documentation. Lookup tables for file paths, badges, Markdown rendering, CI/CD, and CLI tools. Load this skill when working on non-GitHub repos or generating cross-platform docs.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Platform Profiles
PitchDocs defaults to GitHub conventions. Load this skill when the target repository is hosted on GitLab or Bitbucket, or when generating docs that must work across platforms.
## Platform Detection
```bash
[ -f ".gitlab-ci.yml" ] && PLATFORM="gitlab"
[ -f "bitbucket-pipelines.yml" ] && PLATFORM="bitbucket"
[ -d ".github" ] && PLATFORM="github"
PLATFORM=${PLATFORM:-$(git remote get-url origin 2>/dev/null | grep -oE '(github|gitlab|bitbucket)' | head -1)}
```
## Markdown Rendering Compatibility
| Feature | GitHub | GitLab | Bitbucket |
|---------|--------|--------|-----------|
| `> [!NOTE]` callouts | Yes | Yes | **No** — use `**Note:**` bold inline |
| `<p align="center">` | Yes | Yes | Limited |
| `<picture>` dark mode | Yes | Yes | **No** — use single high-contrast image |
| `<details>`/`<summary>` | Yes | Yes | Limited |
| Mermaid diagrams | Yes | Yes (+ PlantUML) | **No** — use pre-rendered SVG |
| Task lists `- [ ]` | Yes | Yes | **No** — renders as plain text |
| Auto TOC | No (manual) | `[[_TOC_]]` | No (manual) |
| Heading anchor format | `#slug-format` | `#slug-format` | `#markdown-header-slug-format` |
| Nested list indentation | 2 spaces | 2 spaces | **4 spaces** |
| HTML permissiveness | Moderate (strips `style`) | More permissive | Restrictive |
## Quick Reference
- **GitLab**: Encode `/` as `%2F` in shields.io paths. Self-hosted instances need `?gitlab_url=` parameter.
- **Bitbucket**: No `<picture>`, no Mermaid, no task lists, use 4-space nested indentation, prefix heading anchors with `markdown-header-`.
- **MCP tools**: `mcp__github__*` are GitHub-specific. For GitLab/Bitbucket, use `glab` CLI, REST API, or git history.
For full lookup tables (template directory mapping, badge URLs, CLI tools, CI/CD, feature availability, raw file URLs, compare URLs, Bitbucket degradation), load `SKILL-tables.md` from this skill directory.Related Skills
pitchdocs
Generate marketing-quality repository documentation from codebase analysis. Scans 10 signal categories, extracts features with file-level evidence, and produces README, CHANGELOG, ROADMAP, and 15+ more docs. Zero runtime dependencies. For AI context file management, see ContextDocs.
visual-standards
Visual formatting standards for repository documentation — emoji heading prefixes, horizontal rules, TOC anchors, callouts, screenshots (device dimensions, HTML patterns, captions, shadows), and image optimisation. Load when generating READMEs with visual elements or working with screenshots.
user-guides
Generates task-oriented user guides and how-to documentation for a repository. Creates docs/guides/ with step-by-step instructions for common workflows, integrations, and advanced usage. Links guides into README.md and CONTRIBUTING.md. Use when a project needs user-facing how-to documentation beyond the README quickstart.
roadmap
Generates ROADMAP.md from project milestones, issues, and boards (GitHub, GitLab, or Bitbucket). Structures content with mission statement, current milestone progress, upcoming milestones, and community involvement section. Use when creating or updating a project roadmap.
public-readme
Generates READMEs with the Daytona/Banesullivan marketing framework — hero section, benefit-driven features, quickstart, comparison tables, and compelling CTAs. Produces docs that sell as well as they inform. Use when creating or overhauling a project README.
pitchdocs-suite
One-command generation and audit of the full public repository documentation set — README, CHANGELOG, ROADMAP, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, issue templates, PR template, and discussion templates. Use when setting up a new repo or auditing an existing one.
package-registry
Documentation guidance for projects published to npm and PyPI package registries. Covers metadata fields that affect registry pages, README cross-renderer compatibility, trusted publishing, provenance badges, and audit checks. Use when a project has package.json or pyproject.toml and is published publicly.
llms-txt
Generates llms.txt and llms-full.txt files following the llmstxt.org specification. Provides LLM-friendly content curation for AI coding assistants (Cursor, Windsurf, Claude Code) and AI search engines. Use when generating or updating llms.txt for a repository.
launch-artifacts
Transforms README and CHANGELOG into platform-specific launch content — Dev.to articles, Hacker News posts, Reddit posts, Twitter/X threads, and awesome list submission PRs. Keeps promotion tethered to code artifacts, not generic marketing. Use when launching or announcing a project release.
geo-optimisation
Generative Engine Optimisation (GEO) patterns for documentation that surfaces correctly in AI-generated answers — citation capsules, crisp definitions, atomic sections, comparison tables, statistics, and semantic scaffolding. Load when optimising docs for AI citation (ChatGPT, Perplexity, Google AI Overviews, Claude).
feature-benefits
Systematic codebase scanning for features and evidence-based feature-to-benefit translation. Extracts what a project does from its code and translates it into what users gain — generates features and benefits sections, "Why [Project]?" content, and feature audit reports. Use when writing a features table for a README, extracting features from code, auditing feature coverage, or answering "why should someone use this project?".
docs-verify
Validates documentation quality and freshness — checks for broken links, stale content, llms.txt sync, image issues, heading hierarchy, and badge URLs. Runs locally or in CI. Use to catch documentation decay before it reaches users.