documentation-portal-html

Plan and orchestrate static HTML documentation portals under Documentation/html/.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill documentation-portal-html
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-portal-html
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/documentation-portal-html_V1.2.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill documentation-portal-html

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and orchestrate a canonical static HTML documentation portal from Documentation/ structure by delegating tasks to specialized documentation skills and enforcing consistency.

Core Features & Use Cases

  • Delegates user requests to the correct documentation skills (bootstrap, roadmap, architecture, RN, portal HTML) and applies transversal rules (naming, hub resync, backups).
  • Generates a portal under Documentation/html/ using the templates TEMPLATE_Docs_html_* and aligns with the canonical Documentation/ hub.
  • Keeps the Documentation hub synchronized by updating Documentation/README_Vx.y.md and moving obsolete artifacts to Documentation/Backup/ as needed.

Quick Start

Plan a new static portal by providing the user request and context; the skill routes to the correct documentation specialist and builds the portal under Documentation/html/ using the canonical templates.

Frequently Asked Questions about documentation-portal-html

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a static HTML documentation portal from existing markdown files?

To generate a static HTML documentation portal, this skill routes your request to specialized documentation agents that apply canonical TEMPLATE_Docs_html_* templates and build the portal under Documentation/html/.

What is the best way to organize and bootstrap a canonical Documentation hub?

Organizing and bootstrapping a Documentation hub involves enforcing a canonical root Documentation/ directory, applying naming rules, and updating the central README_Vx.y.md file to keep all artifacts synchronized.

How does documentation hub resync work when updating static HTML portals?

Documentation hub resync works by updating the central Documentation/README_Vx.y.md file and moving obsolete artifacts to Documentation/Backup/, ensuring the canonical hub stays aligned with the generated HTML portal.

Do I need specific templates to maintain a static HTML documentation portal?

Yes, maintaining a static HTML documentation portal requires using canonical TEMPLATE_Docs_html_* templates to enforce structural consistency and governance across all generated portal pages.

Can I use this approach to migrate obsolete documentation artifacts automatically?

Yes, you can migrate obsolete documentation artifacts automatically by routing maintenance requests through the orchestrator, which moves outdated files into Documentation/Backup/ during the hub resync process.

What are the limitations of orchestrating documentation portals via specialized agents?

Orchestrating documentation portals via specialized agents is limited to static HTML generation under Documentation/html/ and relies on strict canonical directory governance rather than dynamic server-side rendering.