create-tldr-page

Generate tldr pages with 5-8 usage examples from authoritative documentation URLs.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/angryconsultant/Copilot-CLI --skill create-tldr-page-angryconsultant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-tldr-page
Source: https://github.com/angryconsultant/Copilot-CLI/tree/main/skills/create-tldr-page
Command: npx skills add https://github.com/angryconsultant/Copilot-CLI --skill create-tldr-page-angryconsultant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create TLDR pages from verbose documentation by extracting the most relevant command usage and examples, ensuring consistent formatting and accessibility.

Core Features & Use Cases

  • Enforces tldr-pages style templates, including a central URL for upstream docs and representative command usage.
  • Validates required inputs (command name and authoritative URL) and provides clear guidance when missing.
  • Produces compact, example-driven command references suitable for quick lookup in guides or tutorials.

Quick Start

Provide the command name and its authoritative documentation URL to generate a tldr page.

Frequently Asked Questions about create-tldr-page

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

FAQPage Schema
How do I generate a tldr page from official command documentation?

Generate a tldr page by providing the command name and its authoritative upstream documentation URL. The tool validates the URL, extracts relevant usage, and outputs a concise, example-driven command reference.

What is the tldr-pages format for command references?

The tldr-pages format is a compact, templated structure for quick command lookup. It features a central upstream documentation URL alongside 5-8 common usage examples populated with placeholders for easy adaptation.

How many command usage examples should a tldr page contain?

A standard tldr page contains 5-8 common usage examples. These examples use placeholders to represent variables, ensuring the command reference remains compact and adaptable for quick lookup.

Do I need an authoritative URL to create tldr documentation?

Yes, an authoritative upstream documentation URL is a required input. The tool validates the provided URL to ensure the resulting tldr page accurately reflects the official command documentation.

What happens if the command documentation URL is missing or invalid?

If the command documentation URL is missing or invalid, the tldr page generation provides clear guidance. It requires both the command name and an authoritative URL to enforce accurate and consistent formatting.