documentation-static-site-generators
Sub-skill of documentation: Static Site Generators (+2).
Best use case
documentation-static-site-generators is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of documentation: Static Site Generators (+2).
Teams using documentation-static-site-generators 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/static-site-generators/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How documentation-static-site-generators Compares
| Feature / Agent | documentation-static-site-generators | 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?
Sub-skill of documentation: Static Site Generators (+2).
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
# Static Site Generators (+2) ## Static Site Generators - **mkdocs** - Simple, fast Python-based docs - **docusaurus** - Feature-rich React-based platform - **gitbook** - Cloud-hosted documentation ## Document Processing - **sphinx** - Python ecosystem standard - **pandoc** - Universal format conversion ## Presentations - **marp** - Markdown to slides
Related Skills
handle-browser-automation-financial-site-blocks
Workflow for working around Chrome extension blocks on financial sites during data collection tasks
handle-blocked-financial-sites-workaround
Workflow for accessing financial account data when browser automation is blocked on brokerage sites
handle-blocked-financial-sites-data-export
Workflow for extracting data from blocked financial sites when browser automation is restricted
financial-site-bypass-workflow
Workflow for accessing restricted financial sites when browser automation is blocked
static-site-build-artifact-plan-review
Plan-review pattern for static-site fixes where the deployed artifact is generated from source files (e.g. sitemap/robots/static assets). Prevents review churn by separating durable regression checks from one-time migration verification and by validating built output, not just source files.
static-site-brand-identity-migration-tdd
Execute approved static-site brand identity/logo migrations with TDD across canonical content sources, generated deploy output, legacy checked-in HTML, existing stale tests, and build/docs contracts.
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
documentation-contract-plan-hardening
Harden a documentation/contract plan before adversarial review by mapping every issue-scope requirement to independent acceptance criteria and tests, especially for routing/indexing contracts.
orcaflex-static-debug
Troubleshoot and resolve OrcaFlex static analysis convergence issues. Diagnose common problems including line connectivity, tensions, environmental conditions, and numerical instabilities.
aceengineer-website-copy-alignment
Verify proposed copy changes to vamseeachanta/aceengineer-website against canonical sources in workspace-hub (llm-wiki, live site, strategy repo) before shipping. Produces a GitHub issue on the site repo documenting the check with a Match / Drift / Gap verdict.
aceengineer-website-update
Daily automated website updates with competitor analysis and content sync
modular-architecture-documentation
Systematically document multi-module system architectures including module boundaries, CLI commands, and architecture decisions.