ericrisco/rsc-harness / skills/e-signature
e-signature
VerifiedUse when wiring an e-signature flow with DocuSign or Dropbox Sign — picking the SES/AES/QES legal tier, sending a PDF or template for signature, embedded signing, verifying signing webhooks, retrieving the signed PDF plus audit trail. NOT drafting contract text (that is `contracts`), NOT extracting fields from PDFs (that is `document-processing`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.7 KB |
| evals/README.md | markdown | 956 B |
| evals/cases.yaml | config | 3.1 KB |
| references/docusign.md | markdown | 4.2 KB |
| references/dropbox-sign.md | markdown | 3.0 KB |
| references/legal-tiers.md | markdown | 2.9 KB |
| scripts/verify.shexecutable | script | 2.7 KB |
evals/README.md
View on GitHub# e-signature evals
`cases.yaml` holds two kinds of checks. `should_trigger` and `should_not_trigger` are routing assertions for the skill's description: each prompt is matched against the catalog router and we confirm e-signature is (or is not) selected, with `should_not_trigger` naming the real sibling that should win instead. `capability` is a rubric-graded scenario: a model implements the described DocuSign integration and a grader (human or LLM) checks the produced code against the `must_include` list — JWT auth, sandbox base path, envelope with explicit status, HMAC webhook verification on the raw body, idempotency, retrieval of both the signed PDF and the audit trail, no hardcoded secrets, and a deliberate legal-tier choice. Run them through the catalog's standard eval harness; routing cases are automatic, the capability case is graded against a generated artifact (and `scripts/verify.sh` can pre-screen that artifact mechanically).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |