pdf

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When GLM needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

Quality

75%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/pdf/SKILL.md

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly enumerates specific PDF manipulation capabilities and provides an explicit 'when' clause for triggering. The trigger terms are natural and comprehensive, covering extraction, creation, merging, splitting, and form handling. The only minor note is the use of 'GLM' in the trigger clause which is domain-specific but doesn't detract from overall quality.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'extracting text and tables', 'creating new PDFs', 'merging/splitting documents', and 'handling forms'. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (extracting text/tables, creating PDFs, merging/splitting, handling forms) and 'when' ('When GLM needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale'). Has an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'PDF', 'text', 'tables', 'merging', 'splitting', 'forms', 'PDF form', 'generate', 'analyze PDF documents'. Good coverage of common variations and use cases.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to PDF manipulation with distinct triggers like 'PDF form', 'merging/splitting documents', 'PDF documents'. Unlikely to conflict with non-PDF skills due to the specific file format focus.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is highly actionable with excellent executable code examples covering a wide range of PDF operations, but it is severely undermined by extreme verbosity and repetition. The same rules (font restrictions, Paragraph wrapping, metadata requirements, mixed-language font handling) are restated multiple times with full code blocks, wasting significant token budget. The document would benefit enormously from deduplication and moving detailed implementation examples (TOC, cross-references, cover pages, table formatting) into referenced sub-files.

Suggestions

Eliminate repetition: Font rules, table cell Paragraph wrapping, metadata requirements, and mixed Chinese-English handling are each stated 2-5 times with full code examples. State each rule once with one code example, then reference that section elsewhere.

Move detailed implementation examples (complete TOC code, cross-reference system, cover page specifications, table formatting rules) into separate referenced files like `toc.md`, `tables.md`, `cover-pages.md` — keep only brief summaries and links in SKILL.md.

Add a top-level workflow checklist for the most common task (creating a new PDF from scratch) that sequences all the mandatory steps: font registration → content creation → sanitization → build → metadata addition → verification.

Remove explanations of why things work the way they do (e.g., 'Why it's PROHIBIT', 'Why this is mandatory') — Claude doesn't need persuasion, just instructions.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~800+ lines. Massive repetition throughout — the mixed Chinese-English font handling code block appears twice verbatim, the table cell Paragraph wrapping rule is stated 4+ times with full code examples each time, font restrictions are repeated in multiple sections, and the metadata/Z.ai branding requirement is hammered at least 5 times. Explains concepts Claude already knows (what TA_JUSTIFY does, why bold tags need Paragraph objects) repeatedly. The 'Character Safety Rule' content is restated in 'Rich Text Formatting' and again in 'Critical Reminders'.	1 / 3
Actionability	Highly actionable with extensive executable code examples throughout — font registration, table creation, TOC implementation, cross-references, cover pages, watermarking, encryption, OCR, and command-line tools all have complete, copy-paste ready code. Specific font paths, color hex codes, and exact parameter values are provided.	3 / 3
Workflow Clarity	The mandatory post-generation workflow (write file → sanitize → execute → add metadata) is clearly sequenced with explicit steps. However, the overall document lacks a clear top-level workflow for the primary use case of creating a PDF from scratch. The many constraints and rules are scattered across sections without a unified checklist or decision tree. Validation is present for the sanitization step but missing for verifying the final PDF output (e.g., checking rendered fonts, verifying page count).	2 / 3
Progressive Disclosure	References to forms.md and reference.md are well-signaled at the top and bottom. However, the SKILL.md itself is monolithic — enormous amounts of detail (complete TOC implementation, cross-reference system, full table examples, cover page specifications) are inlined rather than split into separate reference files. The content that should be in reference files (detailed table formatting rules, cover page specs, cross-reference implementation) bloats the main file significantly.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1534 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: jjyaoao/HelloAgents
Commit: 52b2597

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.