finish

Automate document finishing, validation, and formatting across Typst, Quarto, and Python workflows.

2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/clearsmog/claude-skills --skill finish-clearsmog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish
Source: https://github.com/clearsmog/claude-skills/tree/main/finish
Command: npx skills add https://github.com/clearsmog/claude-skills --skill finish-clearsmog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Finish skill automates end-to-end document finishing, validation, and formatting to deliver publication-ready output with minimal manual intervention.

Core Features & Use Cases

  • End-to-end pipeline: detect format, compile, render, and apply fixes across Typst, Quarto, and Python-based documents.
  • Visual verification: run a standardized visual QA checklist and re-render pages to validated outputs.
  • Iterative improvement: auto-fix simple issues and route complex cases for human review.

Quick Start

Run the finish pipeline on a document file to compile, verify visuals, and auto-fix issues.

Frequently Asked Questions about finish

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

FAQPage Schema
How do I automate document QA and visual verification for Typst and Quarto pipelines?

Automated document QA for Typst and Quarto pipelines uses a standardized visual checklist to compile, render, and validate pages. It applies auto-fixes for simple issues and routes complex cases for human review to ensure publication-ready output.

What is the best way to auto-fix formatting issues across Python-based document workflows?

The best way to auto-fix formatting in Python-based document workflows is an end-to-end pipeline that detects format, compiles, renders, and applies fixes automatically. This approach requires deterministic frontmatter-driven configuration for safe, auditable re-runs.

Can I use deterministic frontmatter configuration for safe, auditable document re-runs?

Yes, deterministic frontmatter-driven configuration enables safe and auditable re-runs of the document finishing pipeline. This setup ensures consistent execution across compile, render, and validation phases for Typst, Quarto, and Python-based workflows.

How does multi-phase execution work for end-to-end document finishing and validation?

Multi-phase execution for document finishing works by sequentially detecting the format, compiling, rendering, and validating output across Typst, Quarto, and Python workflows. This structured approach standardizes visual QA and iteratively improves the document.

When do I need automated document finishing for content pipelines?

You need automated document finishing when preparing publication-ready output with minimal manual intervention. It is essential for content pipelines using Typst, Quarto, or Python that require standardized visual verification and iterative formatting fixes.

What are the limitations of automated visual QA checklists for document rendering?

The limitation of automated visual QA checklists is that they can only auto-fix simple issues during the render and compile phases. Complex document validation cases cannot be resolved automatically and must be routed for human review.