prompts

Comprehensive Python development skill covering coding standards, CLI development, linting, testing, debugging, refactoring, code review, auditing, documentation, project planning, and bulk operations. Use when writing, reviewing, refactoring, debugging, or documenting Python code; configuring linters; setting up CLI tools; planning features; performing code audits; checking Python antipatterns, forbidden methods, or bad style; or handling bulk operations (10+ files) that benefit from batch workflows instead of per-file iteration.

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

ITU-T-specific contribution document drafting: template structure, header table fields, style-name mapping, equation conventions, and batch workflows. Use when preparing or editing ITU-T contribution .docx files (C-series or TD-series). Delegates formatting rules to sdo-docx-formatting and officecli operations to sdo-docx-operations.

Cross-platform operational guardrails and deterministic helper scripts for officecli OOXML edits on .docx files. Use when editing .docx with officecli raw-set, fixing tab run issues, inserting bookmarks or field codes (SEQ/REF), validating XPath targeting, or preventing destructive raw-set mistakes. Applies across all SDOs -- concrete style names provided by the per-SDO drafting skill.

General 3GPP organization overview, partnerships, scope, and fundamental concepts. Use when working with 3GPP data structures, understanding 3GPP hierarchy, or needing context about 3GPP as an organization.

Change Request procedure, workflow, status tracking, CR database, and step-by-step instructions. Use when working with 3GPP Change Requests to modify specifications, understanding CR lifecycle, or querying CR status.

Meeting structure, naming conventions, quarterly plenaries, and meeting pages. Use when parsing 3GPP meeting data, understanding meeting schedules, or working with meeting metadata from 3GPP portal.

EOL authentication, AJAX login patterns, 3GPP portal data fetching, and session management. Use when accessing protected 3GPP portal resources that require EOL login, fetching TDoc metadata, or working with 3GPP portal APIs.

3GPP release structure, versioning, TSG rounds, and release freeze concept. Use when understanding 3GPP release numbering, TSG round schedules, or finding specifications in releases.

TS and TR numbering, spec file formats, FTP directory structure, and accessing 3GPP specifications. Use when working with 3GPP specification numbering, finding spec files, or understanding spec directory organization.

TDoc patterns, filename conventions, metadata structure, HTTP/FTP server access, and TDoc identification. Use when crawling TDocs from FTP directories, parsing TDoc metadata from portal, or validating TDoc numbers.

Working group nomenclature, tbid/SubTB identifiers, subgroup hierarchy, and TSG structure. Use when working with 3GPP working groups, parsing meeting codes, or understanding TBID mappings.

ETSI-specific deliverable drafting conventions: document structure, clause ordering, requirements writing (shall/should/may), figures/tables/equations, annexes, and ETSI style-name mapping. Use when preparing or editing ETSI deliverable .docx files (TS, ES, EN, TR, EG, SR, GS). Delegates formatting rules to sdo-docx-formatting and officecli operations to sdo-docx-operations.

Reusable .docx formatting conventions for formal standardization documents. Use when formatting headings, notes, enumerations, tables, figures, cross-references, citations, and text in technical standards documents. Applies across SDOs -- concrete style names are provided by the per-SDO drafting skill. Triggers include "format this document", "apply styles", "add cross-references", "insert table/figure", "format notes or citations".

ITU-T contribution and TDoc submission procedures, deadlines, liaison statement format, and IPR requirements. Use when the agent needs to understand how to submit, format, or process ITU-T contributions (C-series documents), TDocs (Temporary Documents), or liaison statements. Covers submission deadlines, translation rules, patent/copyright declarations, and electronic posting. Sources: Rec. ITU-T A.1 (09/2019) clause 3.

ITU-T Recommendation structure, approval processes, amendment/corrigendum procedures, and ITU-T | ISO/IEC common text conventions. Use when the agent needs to understand how ITU-T Recommendations are structured (clause order, element types, annex conventions), approved (TAP/AAP), amended, or how joint ITU-T/ISO/IEC texts work. Sources: Rec. ITU-T A.1 (09/2019) + Rules for presentation of ITU-T | ISO/IEC common text (2014).

Mechanical writing conventions for formal standards documents across all SDOs (3GPP, ETSI, ITU-T). Use when drafting or revising text to ensure consistent spelling (-ize/-ise), hyphenation, number formatting, capitalization, abbreviations, list formatting, proper names, and non-discriminatory language. Complements sdo-writing-style (prose quality) with mechanical correctness rules. Sources: ITU English Language Style Guide (2024).

Skill family for agent-assisted software development workflows. Includes workspace isolation (git-worktrees), parallel debugging (dispatching-parallel-agents), structured multi-task development (subagent-driven-development), and lightweight code review (requesting-code-review). Install individual skills based on workflow needs.

Parse, convert, chunk, and analyze documents using Docling. Use this skill when the user provides a document (PDF, DOCX, PPTX, HTML, image) as a file path or URL and wants to: extract text or structured content, convert to Markdown or JSON, chunk the document for RAG ingestion, analyze document structure (headings, tables, figures, reading order), or run quality evaluation with iterative pipeline tuning. Triggers: "parse this PDF", "convert to markdown", "chunk for RAG", "extract tables", "analyze document structure", "prepare for ingestion", "process document", "evaluate docling output", "improve conversion quality".

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Insert SVG images into Word .docx files. Use when the user or coding agent needs to add, embed, or update an SVG graphic inside a .docx document. Triggers include "insert SVG into docx", "embed SVG in Word document", "add vector graphic to docx", "SVG image in template", "requests to convert SVG to PNG for docx", or any request explicitly mentioning embedding or inserting SVG graphics into .docx files.

Use this skill any time a .pptx file is involved — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions 'deck,' 'slides,' 'presentation,' or references a .pptx filename.

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file; create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path and wants something done to it or produced from it. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, or Google Sheets API integration.

3GPP-specific TDoc authoring conventions: metadata schema, template substitution, revision workflow, DOCX property sync, project layout, and 3GPP style-name mapping. Use when preparing, updating, or validating 3GPP TDoc .docx files for meeting submissions. Delegates formatting rules to sdo-docx-formatting and officecli operations to sdo-docx-operations.

ETSI organisation overview, deliverable types, standards development lifecycle, and key roles. Use when the agent needs context about how ETSI works: Technical Committees, deliverable types (TS, ES, EN, HS, TR, EG, SR, GS), approval processes, the standards development lifecycle (Work Item through publication), or ETSI-specific terminology. Sources: ETSI Guide to Writing World Class Standards + ETSI Directives.

ITU-T organizational structure, document types, terminology, roles, and meeting procedures. Use when the agent needs context about how ITU-T works: study groups, working parties, rapporteurs, Question/WTSA/TSAG/TSB concepts, meeting procedures, or ITU-T document type definitions (Recommendation, amendment, corrigendum, annex, appendix). Sources: Rec. ITU-T A.1 (09/2019).

ITU-T patent policy, IPR disclosure, and licensing declarations for standardization contributors. Covers the Common Patent Policy for ITU-T/ITU-R/ISO/IEC (2022), the three licensing options (RF, RAND, refusal), Patent Statement and Licensing Declaration Forms (individual and general), disclosure obligations at meetings and after approval, the ITU Patent Information database, cover sheet notification text, and ITU neutrality principles. Use when the agent needs to understand patent disclosure requirements, fill in declaration forms, add patent notices to Recommendation drafts, or handle SEP-related procedures during ITU-T standards development.

Bootstrap and maintain an agent-based document drafting project for any SDO. Use when starting a new standards contribution, setting up project structure (PLAN.md, AGENTS.md, directory layout), syncing metadata between PLAN.md and .docx properties, or detecting whether a project is new vs. ongoing. Provides common project infrastructure; SDO-specific templates and header structures live in the per-SDO drafting skill.

General writing principles for formal standardization documents across SDOs (3GPP, ETSI, ITU-T). Use when drafting or revising prose content for standards contributions, technical reports, or meeting documents. Covers specificity, fact discipline, anti-genericity, register, structure, and revision checks. Does NOT cover .docx formatting -- see sdo-docx-formatting for style rules.

Universal documentation standards and best practices for software projects

Pre-write workflow to prevent semantic code duplication. Use BEFORE creating new utility functions, shared modules, or helper code to verify equivalent capabilities don't already exist in the codebase. Requires maintaining CODE_INDEX.md as a capability index organized by purpose (not file location).

Language-agnostic behavioral guidelines to reduce common LLM coding mistakes. Use for ANY coding task (all languages) to avoid overcomplication, make surgical changes, surface assumptions before coding, and define verifiable success criteria. Applies behavioral rigor—separate from language-specific technical standards.

Detect and eliminate generic, low-quality "AI slop" patterns in natural language, code, and design. Use when REVIEWING existing content (text, code, or visual designs) for quality issues, cleaning up generic patterns, or establishing quality standards. Focuses on pattern detection—not content creation.

Dispatch multiple subagents in parallel when facing 2+ COMPLETELY INDEPENDENT tasks that can be worked on without shared state, sequential dependencies, or cross-task communication. Use for investigating unrelated failures (different test files, different subsystems, different bugs) where each subagent works on a different problem domain.

Lightweight standalone code review workflow. Use for ad-hoc reviews outside structured development workflows—after completing single tasks, before merging to main, or when stuck and needing a fresh perspective. For structured multi-task development, use subagent-driven-development instead (which includes integrated review stages).

Structured multi-task development workflow with integrated two-stage review (spec compliance + code quality). Use when executing implementation plans in the CURRENT session with independent tasks. Dispatches fresh subagent per task with built-in review gates. For ad-hoc single reviews, use requesting-code-review instead.

Create isolated git worktrees for feature development with automatic directory selection and safety verification. Use when starting feature work that needs isolation from the current workspace, or when setting up before executing implementation plans that require a clean branch environment.

Review existing skills and suggest improvements. Use when asked to review, audit, or improve a skill — validates against Agent Skills spec and best practices. Also triggers when drafting or creating a new skill. Run `uvx skills-ref validate` to check spec compliance.

MCP server integration for CytoScnPy code metrics analysis. Use when configuring CytoScnPy MCP server for AI assistants (Claude, Cursor, Copilot), setting up VS Code extension integration, or exposing code quality tools via MCP. Triggers on: mcp-cytosnpy, cytoscnpy mcp-server, MCP server setup, AI assistant code analysis integration, VS Code extension configuration.

CLI tool for CytoScnPy - code metrics analysis for Python projects. Use when running code quality scans, calculating cyclomatic complexity, Halstead metrics, maintainability index, or generating project statistics. Triggers on: cytoscnpy commands, code metrics analysis, complexity reports, maintainability scoring, or MCP server setup for LLM integration.