Scribe Mastery (Super Skill)

Name: Scribe Mastery (Super Skill)
Availability: InStock
Author: wtyler2505

Audits Scribeproject folders and generates missing documentation artifacts in the correct sequence.

1|Updated Feb 21, 2026

Search Tags:#automation #workflow #documentation #markdown #project-management #scribe

Ready to run

npx skills add https://github.com/wtyler2505/ProtoPulse --skill scribe-mastery-super-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Scribe Mastery (Super Skill)
Source: https://github.com/wtyler2505/ProtoPulse/tree/main/.agents/skills/scribe-mastery
Command: npx skills add https://github.com/wtyler2505/ProtoPulse --skill scribe-mastery-super-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often waste time coordinating multiple scribes and manually advancing project stages. Scribe Mastery acts as a Managing Editor, auditing the scribe/<project>/ folder and proactively driving the pipeline forward.

Core Features & Use Cases

Pipeline Inference: Inspects scribe/<project>/ to determine missing or pending artifacts (RESEARCH.md, BLUEPRINT.md, DRAFT.md, CRITIQUE.md, FINAL.md) and suggests or creates needed files.
Autonomous Progression: Generates missing stages in the correct order, preventing skipped steps and keeping projects on track.
Workspace Context Integration: Reads broader knowledge sources to inform drafting and versioning for accurate, context-aware documentation.

Quick Start

Enable Scribe Mastery to audit the scribe/<project>/ folder and automatically generate BLUEPRINT.md, DRAFT.md, CRITIQUE.md, and FINAL.md as needed.

Frequently Asked Questions about Scribe Mastery (Super Skill)

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

FAQPage Schema

How do I automate markdown documentation workflows to prevent skipping project stages?▼

Automating markdown documentation workflows requires a system that audits project folders and enforces sequential progression. This skill inspects scribe directories and generates missing artifacts like DRAFT.md or CRITIQUE.md to prevent skipped steps.

What is the best way to manage multiple scribes and ensure complete project documentation?▼

Managing multiple scribes effectively requires a centralized pipeline that infers missing artifacts. This skill acts as a managing editor, auditing scribe project folders and autonomously generating required markdown files to ensure complete documentation progression.

How do I enforce markdown formatting and 80-character line length in documentation pipelines?▼

Enforcing markdown formatting and 80-character line length in documentation pipelines requires automated style guardrails. This skill audits generated markdown files and applies strict formatting rules to maintain consistency across project artifacts.

Can I automatically generate missing markdown files like BLUEPRINT.md and FINAL.md in order?▼

Yes, you can automatically generate missing markdown files like BLUEPRINT.md and FINAL.md in strict order. This skill inspects existing project artifacts and creates pending files sequentially to ensure error-free progression.

Does this documentation pipeline tool work without external dependencies?▼

Yes, this documentation pipeline tool operates without external dependencies. It autonomously manages project workspaces by reading broader knowledge sources and isolating folders to maintain guardrails without requiring additional packages.