upskill

Generates standardized, project-specific SKILL.md files from analyzed repositories and topics.json.

10|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/thermiteau/maverick --skill upskill-thermiteau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upskill
Source: https://github.com/thermiteau/maverick/tree/main/skills/upskill
Command: npx skills add https://github.com/thermiteau/maverick --skill upskill-thermiteau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates standardized, project-specific SKILL.md files for each skill topic by analyzing the repository, reducing manual skill documentation work and ensuring consistent guidance across projects.

Core Features & Use Cases

  • Scans topics.json and the repository to produce a per-topic SKILL.md in docs/maverick/skills.
  • Writes root-level or package-level skills depending on whether the codebase is a single-repo or mono-repo.
  • Uses an existing best-practice skill as a reference to shape recommended skills when no project-specific implementation exists.

Quick Start

Initiate the upskill command to generate all topic SKILL.md files across the repository.

Frequently Asked Questions about upskill

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

FAQPage Schema
How do I auto-generate project-specific skill documentation for my repository?

To auto-generate project-specific skill documentation, run the upskill command to scan topics.json and your repository, producing per-topic SKILL.md files in docs/maverick/skills automatically.

How does automated skill generation work for mono-repo codebases?

Automated skill generation for mono-repos detects repository topology and writes package-level skills under docs/maverick/skills, scaling across single-repo and mono-repo layouts appropriately.

Can I generate recommended skills using an existing best-practice skill as a reference?

Yes, you can generate recommended skills using an existing best-practice skill reference to shape the output when no project-specific implementation exists within the repository.

What's the best way to ensure consistent project documentation across multiple skills?

The best way to ensure consistent project documentation is auto-generating standardized SKILL.md files per topic, reducing manual skill documentation work across the entire project.

Do I need a topics.json file to generate per-topic project skills?

Yes, you need a topics.json file because the skill generation pipeline relies on it alongside repository topology detection and best-practice references to produce the final SKILL.md outputs.