rossum-sa
Claude Code plugin for Rossum.ai workflows — skills, references, and MCP tools for Rossum implementations
Plugin rossum-sa from marketplace rossumai-claude-marketplace in rossumai/claude-marketplace. Commands read from the repo's manifest — yesterday.
This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.
What it installs
Skills (35)
analyzeAnalyze a Rossum.ai implementation to detect common configuration errors and issues. Discovers the full implementation first, then checks for known problems. Use when reviewing a customer's setup for correctness. Triggers on requests like "check this implementation", "find issues", "review this setu
approval-workflows-referenceRossum approval-workflows reference — how documents route through an ordered chain of approval steps (workflow → ordered workflow_steps → workflow_runs, logged as workflow_activities). Covers the read-only public API (GET workflows / workflow_steps / workflow_runs / workflow_activities, plus the one
automation-reportTurn Rossum queue-level automation analytics into a detailed, actionable report with concrete recommendations. Uses automation_insights (available on every queue) and opportunistically upgrades the analysis when automation_projections responds. Use when diagnosing why automation is low or planning t
b2brouter-reconciliationUse when checking whether e-invoices received on the B2Brouter network all landed in Rossum — "B2Brouter reconciliation", "did we lose any e-invoices", "reconcile e-invoices against Rossum", "are all invoices from the e-invoicing network in Rossum", "check for missing e-invoices", "invoice arrived a
business-rules-referenceRossum business-rules & validation reference — the two ways to validate extracted data and block automation: native Rossum Rules (the /v1/rules entity — trigger_condition + actions[], FIRE-vs-PASS polarity, lifecycle, rule events — validation, annotation_imported/confirmed/exported and the outcome e
coding-best-practicesUse when reviewing, auditing, or writing Rossum serverless hook functions (custom Python extensions) for code quality, security, and correctness
coupa-baseline-referenceCoupa Integration Baseline (CIB) — Complete Reference & Working Guide. Pre-configured Rossum-to-Coupa AP invoice processing solution, covering both baselines in production — CIB 1.x (one workspace, two taxation queues) and CIB 2.0 (six workspaces, seven queues — the two baseline queues, an E-invoici
coupa-bulk-replicationBulk-replicate Coupa master data into Rossum Data Storage, bypassing import hooks that time out on large datasets
data-storage-referenceRossum Data Storage API reference — MongoDB-compatible REST API for collections, CRUD operations, find, aggregate, bulk_write, indexes, and Atlas Search indexes. Use when querying or managing data in Rossum's Data Storage service directly via API.
dead-codeFind unused hooks, formulas, rules, labels, and engines in a Rossum implementation. Runs a deterministic detector against a local prd2 tree and produces a delete-list report. Use when pruning a customer's configuration. Triggers on "dead code", "unused extensions", "what is not used", "cleanup", "pr
documentDocument a Rossum.ai implementation — produce a structured technical reference covering architecture, hooks, queues, integrations, formulas, and troubleshooting. Use this skill whenever the user wants to understand, describe, summarize, or write up what an implementation does. Triggers include reque
email-body-converter-referenceEmail Body Converter (also spelled "convertor") reference — Rossum's hosted webhook extension that converts an inbound email's HTML body into a PDF and imports it as a new document/annotation, for when the invoice or order data lives in the email body itself rather than in an attachment. Covers setu
evaluate-namingsUse when evaluating or auditing naming conventions of Rossum workspaces, queues, hooks, schema fields, and MDH datasets in a prd project
export-pipeline-referenceRequest Processor (export pipeline) configuration reference for Rossum. Covers the multi-stage JSON-based engine for integrating Rossum with external APIs — stages, variable templating, evaluate conditions, get_content sources, call_api with auth/iteration/file uploads, response handlers (JMESPath/X
implementPlan and execute a Rossum integration project end-to-end. Guides through scoping, schema design, MDH configuration, hook development, business rules, export pipelines, and deployment. Use when starting a new implementation, adding a major feature, or onboarding to an existing project. Triggers on re
init-claude-mdGenerate a project-specific CLAUDE.md for a pulled Rossum prd2 project so future Claude Code sessions immediately recognize the directory as a Rossum implementation and apply the right safety rules. Inspects environments, queues, hooks, schemas, and integration targets locally — no remote API calls.
iterateIterate on a Rossum deliverable (hook, formula, rule, schema change) against a specific annotation until a stated goal is met. Provides the re-fire primitives via MCP — soft re-fire (start → content/validate → cancel), status toggle, in-place re-extract, re-upload, and export re-fire (status → expor
mdh-referenceRossum Master Data Hub (MDH) API reference and matching query design guide. Covers dataset CRUD, fuzzy search, hook configuration model (MatchConfig, mapping, result actions, query cascades), query design rules, score normalization, and real-world matching examples. Use when building or debugging MD
mongodb-referenceMongoDB query language reference tailored for Rossum. Covers find operators, regex patterns, aggregation pipeline stages, expression operators, Atlas Search ($search with fuzzy, compound, dynamic thresholds, embedded documents), $function, $lookup, $unionWith, practical matching patterns, data type
netsuite-referenceRossum NetSuite integration reference. Covers the Rossum-hosted SOAP connector (svc/netsuite-v3) — import webhooks (search / getAll payloads, basic vs advanced searches, advanced_search_internal_id_jmespath, {last_modified_date} incremental sync, async_settings), the export webhook (upsert VendorBil
parts-indexIndex of the rossum-sa parts library — vetted, parameterized, composable building blocks (capture, master-data import, matching, export) lifted from the reference packs and from production implementations. Consult when assembling a Rossum implementation to reuse a known-good pattern instead of writi
plugin-feedbackReport friction with the rossum-sa plugin as a sanitized, human-confirmed GitHub issue or anonymous maintainer-reviewed report. Use when the SA hits a capability gap, a tool bug, or a wrong/ missing Rossum fact, or when the friction detector offers to log it. Triggers on "log plugin feedback", "repo
prd-referenceprd2 CLI reference for managing Rossum configurations across environments. Covers pull, push, deploy, purge commands, credentials, deploy files, attribute overrides, and project structure. Use when working with prd2, deployment workflows, or Rossum environment management.
queue-engine-bindingBind Rossum queues to custom extraction engines via the public API. Four modes — convert a generic-engine queue to a new custom engine, create a new engine-bound queue (greenfield), attach a queue to an existing engine, or revert to the generic engine. Use when changing which extraction engine a que
rdc-referencerdc (Rossum Deployment as Code) CLI reference — the newer alternative to prd2 for snapshotting a Rossum org as files and deploying it. Covers telling an rdc project from a prd2 project, the envs/<env>/ tree with slug-named files and rdc:// references, `rdc sync` (three-way merge, dry-run, --no-push
refine-deploymentRefine Rossum prd2 deploy files by auto-filling missing target IDs, generating attribute overrides for naming conventions and environment-specific settings, and highlighting missing target objects. Use when preparing a deploy file for a Rossum environment migration.
render-export-templateAuthor, render, and iterate on Rossum Custom Format Templating export templates — the legacy Jinja2 templates stored inside an export hook's settings.export_configs that turn an annotation into a flat file, CSV, XML, EDI, or custom JSON. Pull a template out of a hook into a local file, render it fai
rossum-referenceComplete Rossum.ai platform reference including API, architecture, concepts, schemas, extensions, and workflows. Use when answering questions about Rossum, writing Rossum integrations, configuring queues/schemas/hooks, or working with the Rossum API.
sap-referenceSAP integration guide for Rossum. Covers the SAP product landscape (S4 HANA Public/Private Cloud, ECC, Ariba, VIM, BTP), AP/AR terminology, master data scoping, and — measured on three real integrations — the three shapes a Rossum–SAP integration takes (OData through a BTP API gateway; customer HTTP
sfi-referenceStructured Formats Import (SFI) reference for Rossum. Covers end-to-end setup of the SFI extension for processing XML, JSON, and e-invoice documents (ZUGFeRD, X-Rechnung UBL/CII). Includes MIME type configuration, hook setup with environment URLs, field mapping with XPath/JSONPath selectors, documen
test-behavioral-equivalenceVerify that changes to a Rossum implementation preserve behavior. Captures a "before" snapshot of annotation outputs, replays the same documents against the upgraded implementation, and diffs the "after" outputs against the snapshot. Use after an upgrade, refactor, or any change intended to be behav
txscript-referenceRossum field-expression reference for TxScript serverless hooks, native Rossum Rule trigger_condition expressions, and schema-field formulas. Covers (a) TxScript Python 3.12 API, (b) the native Rule trigger_condition expression language and the defensive is_empty guard convention (the Rule entity, a
upgradeUpgrade deprecated Rossum extensions to modern equivalents and bump old Python runtimes on function hooks to python3.12. Finds old Copy & Paste, Find & Replace, Value Mapping, and Date Calculation extensions and produces replacement formula fields with migration steps. Use when modernizing a custome
workday-referenceRossum Workday connector reference. Covers the Rossum-hosted SOAP connector (svc/workday) — export and import hook wiring and secrets, the wsdl block and impl-vs-prod tenant domains, the mapping template language (IF_SCHEMA_ID, FOR_EACH_SCHEMA_ID, DATAPOINT_MAPPING operations and the @{schema_id} sh
write-sowGenerate or review a Statement of Work (SOW) for a Rossum.ai implementation project. Scopes from a matching recipe so the questions are the ones a build actually stalls on, and reports which decisions the SOW leaves open. Use when the user wants to create, scope, or review a SOW or project proposal.
MCP servers (1)
rossum-apiruns: python3 ${CLAUDE_PLUGIN_ROOT}/mcp-servers/rossum-api/server.py
Hooks (5)
- PostToolUse
python3 ${CLAUDE_PLUGIN_ROOT}/hooks/detect_friction.py
- PostToolUse
python3 ${CLAUDE_PLUGIN_ROOT}/hooks/rossum_auth_guard.py
- PostToolUseFailure
python3 ${CLAUDE_PLUGIN_ROOT}/hooks/detect_friction.py
- UserPromptSubmit
python3 ${CLAUDE_PLUGIN_ROOT}/hooks/detect_friction.py
- Stop
python3 ${CLAUDE_PLUGIN_ROOT}/hooks/detect_friction.py
Maintain rossum-sa?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.