メニュー
Given a sensible-hq/sensible PR number, find any new/modified extractor test directories and upload their configs and golden PDFs to the Sensible account via the API.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generates and publishes a monthly Sensible product changelog. Invoke whenever the user wants to write, draft, or publish a monthly changelog, or mentions writing up a release summary given a list of PRs. The user will provide PR numbers (from the frontend or backend GitHub repo, or both) and optionally a list of doc topic URLs. The skill structures the input, fetches PR context, drafts the changelog in Sensible's house style, gets user approval, then publishes as a hidden draft to readme.com.
Creates or updates OpenAPI JSON spec files in the /reference directory of sensible-docs, based on backend PRs from sensible-hq/sensible. Use this skill whenever the user provides PR numbers or GitHub URLs from the backend repo and wants to document new API endpoints, update existing endpoint schemas, or add new fields to an existing API reference. Also triggers when the user mentions "new API", "update the spec", "API reference from PRs", "write a spec for [feature]", or provides a list of PRs and asks to document them. This skill handles the end-to-end workflow: reading PRs, extracting API surface changes from diffs and Zod/TypeScript schemas, drafting OpenAPI 3.0.3 JSON, creating supporting markdown files, and updating _order.yaml navigation files.
Given a sensible-hq/sensible PR number, analyze the engine/API changes and update the sensible-docs repo accordingly, then open a PR. Handles both updating existing pages and creating new pages. If you already know which type of change is needed, use update-existing-doc or create-new-doc directly for a more focused workflow.
Generates a "how to extract data from X" blog post draft for Sensible. Takes a document type as input and either fetches the matching prebuilt config from the open-source library, or accepts an explicit config file/URL and optional PDF path via --config and --pdf flags. Invoke whenever the user wants to write or draft a "how to parse/extract X" blog post.
Checks Sensible documentation files for terminology violations before publishing. Invoke whenever the user wants to check, review, validate, or proofread a Sensible doc (changelog, reference page, integration guide, concept topic), or asks whether a file uses correct terminology. Accepts a file path, pasted content, or both. Also invoke if the user asks to "run the checker" or "check terminology".
Generates or refreshes the Sensible integration guide template by reading existing integration guide pages from the published docs and analyzing their conventions. Use this skill whenever asked to generate, update, or refresh the integration guide template, or when .claude/style-guide/integration-guide-template.md is missing or stale. Also invoke before writing a new integration guide from scratch.
| name | upload-pr-extractor |
| description | Given a sensible-hq/sensible PR number, find any new/modified extractor test directories and upload their configs and golden PDFs to the Sensible account via the API. |
| argument-hint | <pr-number> |
| disable-model-invocation | true |
| allowed-tools | Bash(gh pr diff:*), Bash(gh pr view:*), Bash(python3:*), Bash(python:*), Glob, Read |
You are uploading extractor test configs and golden PDFs from a sensible-hq/sensible pull request to the Sensible account.
The PR number is: $ARGUMENTS
Fetch the PR diff and identify any files added or modified under extractors/:
gh pr diff $ARGUMENTS --repo sensible-hq/sensible
Look for file paths matching extractors/{customer}/{doctype}/.... Collect each unique {customer}/{doctype} pair.
Only proceed with directories that have both a config JSON file (e.g. all.json) and at least one golden PDF in goldens/. Skip any that are missing either.
The sensible engine repo is at ../sensible relative to this repo (sensible-docs). For each {customer}/{doctype} pair found:
../sensible/extractors/{customer}/{doctype}/*.json../sensible/extractors/{customer}/{doctype}/goldens/*.pdfUse Glob or Read to confirm the files exist before proceeding.
For each config file and each golden PDF, call the upload script:
python3 scripts/upload_pr_extractor.py \
--doc-type {doctype} \
--config ../sensible/extractors/{customer}/{doctype}/{config}.json \
--golden ../sensible/extractors/{customer}/{doctype}/goldens/{golden}.pdf \
--config-name {config_stem}
The script uses SENSIBLE_API_KEY from the environment. It will:
If there are multiple config files, run the script once per config. If there are multiple golden PDFs, run the script once per golden (reusing the same config each time).
Tell the user: