Skip to content

JasonColapietro/suede-creator-skills / skills/suede-ops-assessment

suede-ops-assessment

Verified

Suede Operations Assessment Skills: map real work, silos, friction, ownership, costs, and adoption signals from operator evidence. Use when asked "where is our team losing time" or to rank operational opportunities before designing automation. NOT FOR: choosing and building the target architecture (suede-ops-architecture), auditing requester-supplied figures, or unapproved system access.

FileKindSize
CARD.mdmarkdown4.6 KB
SKILL.mdskill md12.3 KB
agents/openai.yamlconfig719 B
evals/evals.jsonconfig4.3 KB
references/interview-guide.mdmarkdown4.6 KB
references/worked-contract.mdmarkdown2.4 KB

references/worked-contract.md

View on GitHub
# Suede Operations Assessment Skills: Worked Contract

This is a synthetic application scenario, not a client result or a required output filename. Adapt the values to the supplied evidence. The skill's existing output format and authority boundaries apply.

## Input

A support team reports twelve weekly escalations. Agents say each takes twenty minutes; a manager describes only the final approval step. The scope is escalation handling, not the entire company.

## Expected output

Return the Output Contract with the operator process map, silo inventory, friction quantified in the supplied units, ranked opportunities, engagement signal, and a thirty-day adoption observation plan. Preserve the team's figures as given and distinguish every inferred process step or estimate with [assumed].

## Missing input and recovery

If no operator is available, record that the map reflects a manager account and leave operator-only steps missing. Do not replace the supplied time with an industry benchmark. A system outside authorized access stays outside the read set; use an interview or export request instead.

## Validation

Reconcile the unit math: twelve escalations times twenty minutes is four hours per week. Check ownership for intake, action, approval, and exception handling. Ensure any agent-created benchmark is sourced or [assumed], never presented as the team's measurement.

## Detailed scope and routing

Suede operations-assessment discipline that maps how work actually happens before anyone designs a system: floor-level interviews with the people who do the work, an inventory of every silo including spreadsheets and inboxes used as databases, friction quantified in the requester's own numbers, opportunities ranked by annual value against build complexity, and adoption watched for the thirty days after launch. Use when nobody can answer what to automate, when an operation needs auditing before a build, when tribal-knowledge and key-person risk has to surface, or when a shipped system is quietly being routed around. NOT FOR: deciding what to build and in what order once the map exists (use suede-ops-architecture); researching external customers rather than internal operators (use suede-customer-research); lead lifecycle, scoring, and CRM routing rules (use suede-revops); product instrumentation and dashboards (use suede-analytics); getting a new user to first value (use suede-onboarding).
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall