Question: is a vendor-backed document processing skill in scope for skills/.curated? #268
Description
Summary
I am considering contributing a document-processing skill for Codex built around Nutrient DWS, and I wanted to confirm whether this type of third-party or vendor-backed skill is in scope for skills/.curated before opening a PR.
Why I am asking first
The repo already includes built-in document-oriented skills like pdf and doc, so I do not want to submit something redundant if the curated catalog is intended to stay narrower.
The potential contribution is differentiated less by generic PDF handling and more by managed workflows such as:
- PDF generation from HTML and remote URLs
- Office, image, and PDF conversion
- OCR and structured extraction
- deterministic and AI-assisted redaction
- form filling and digital signatures
- archival and accessibility outputs like PDF/A and PDF/UA
- optimization and linearization for delivery
Proposed shape
The skill is structured as:
- one compact umbrella
SKILL.mdrouter - focused
references/docs for generation and conversion, OCR and extraction, security and forms, compliance and optimization, and workflow recipes - optional Codex App metadata via
agents/openai.yaml
The goal is to keep discovery and invocation simple while keeping the top-level skill token-efficient.
Question
Would a skill like this be considered in scope for contribution to skills/.curated, or would you prefer that it remain an external, community-maintained skill referenced outside the main curated catalog?
If it is in scope, I am happy to open a PR with a minimal, well-scoped version and adjust it to match your preferences.