alisonjieli-png
UserBaltor: a reviewed library of skills, AGENTS.md sections, subagents, commands, hooks and protocol server settings that coding agents search and fetch for each step. This repository holds Loop Engine, its open-source engine.
Categories
Indexed Skills (45)
carry-a-sales-promise-into-delivery
Reconcile customer-facing commitments with current delivery scope and owners before a sales handoff becomes an untracked promise.
compare-acquisition-channels-for-one-segment
Compare candidate customer-acquisition channels for one defined segment using reach, permission, cost, conversion evidence, and attribution limits.
gate-a-product-launch-across-teams
Build a cross-team launch gate map covering the actual customer journey, communications, billing, support, and fallback before a public announcement.
prepare-a-support-escalation-packet
Turn a bounded support case into a reproducible, privacy-scoped escalation packet for an engineering or operations owner.
qualify-a-partner-integration-proposal
Evaluate a proposed partner integration against bilateral value, data boundaries, responsibilities, and failure handling before implementation commitments.
qualify-an-invited-pilot-cohort
Select a proposed invited pilot cohort against stated eligibility, support capacity, and learning goals before invitations or account changes occur.
reconstruct-a-buyer-decision-path
Map evidence for an organizational purchase decision, separating evaluators, approvers, blockers, and unknown gates without inferring authority from job titles.
synthesize-discovery-interviews-with-counterexamples
Build a traceable need hypothesis from a bounded set of customer interviews, counting people rather than repeated remarks and keeping counterexamples visible.
adjudicate-a-protocol-tool-effect-request
Review one proposed protocol-tool operation against its exact effects, target, parameters, grants, and approval before a broker may execute it.
compile-a-native-material-placement-plan
Plan exact native destinations for selected harness material under a stated client layout, refusing collisions and unsupported file kinds before installation.
design-catalogue-withdrawal-checks
Specify negative checks for withdrawing a harness item across search, grants, body reads, cached manifests, and older release images.
revalidate-output-allocation-on-model-fallback
Review output capacity and remaining allowance for a proposed model route fallback without carrying limits or context eligibility across providers.
scope-a-step-credential-lease-to-physical-use
Check that a fresh harness's credential reference is bound to one step, recipient, operation class, lifetime, and physical-use limit.
specify-an-isolated-harness-startup-probe
Design a source-discovery probe for a fresh harness that can detect selected material and unexpected inherited instructions before a task run.
bound-obsolete-stock-by-support-horizon
Classify revision-specific stock exposure using supplied compatibility and support rules. Use when older parts are being called obsolete without checking supported demand.
compare-satisfaction-waves-by-respondent-mix
Test whether a satisfaction trend survives comparable segment mixes and survey response patterns. Use before calling an overall survey increase a like-for-like improvement.
qualify-a-prebuilt-application-against-required-seams
Check a prebuilt application against mandatory interfaces, capabilities, deployment limits, and failure behavior. Use before recommending adaptation instead of a new build.
allocate-scarce-stock-by-promised-service
Propose a bounded allocation of scarce stock to competing orders under supplied service promises. Use when available units cannot cover all committed demand.
compare-distribution-paths-with-failure-costs
Compare candidate distribution paths using supplied cost, time and disruption evidence. Use when a cheapest quoted route may fail the delivery requirement.
explain-work-package-cost-variance
Explain project cost variance by work package, period and committed versus incurred amounts. Use when a single total hides timing or scope changes.
bridge-forecast-driver-changes
Explain the movement between two forecast versions through named driver changes and a residual. Use when a revised demand, revenue, or workload forecast needs an auditable change explanation.
reconcile-inventory-availability
Reconcile physical stock, reservations, holds, and available quantity at one cutoff. Use when inventory appears sellable twice or a displayed availability exceeds usable stock.
reconcile-order-fulfillment-quantities
Reconcile accepted order-line quantity with cancellations, partial shipments, returns, and open obligation. Use when orders look complete from one shipment or duplicate events inflate fulfillment.
reconcile-record-flow-across-stages
Reconcile logical records through an ingest, validation, and publication flow. Use when a batch total looks complete but records may be rejected, duplicated, or missing between stages.
reconstruct-service-clock-from-status-intervals
Reconstruct elapsed and chargeable service time from start, pause, resume, and completion records. Use when a support or operations service clock disagrees with wall time.
trace-field-lineage-to-a-measure
Trace one reported measure to source fields and transformation versions. Use when a report cell needs an explainable path through filters, joins, derivations, or overrides.
validate-source-to-target-field-map
Review a proposed mapping from one source feed to a target schema. Use when field names match but units, row meaning, enumerations, nulls, or time semantics may differ.
reconcile-native-material-use-evidence
Reconcile offered, fetched, placed, discovered, loaded, used, and independently verified harness material from separate records.
diagnose-process-constraint-from-flow
Locate a candidate flow constraint from arrivals, completions, and queues. Use when a slow-looking stage is called the bottleneck without throughput evidence.
reconcile-account-difference-to-postings
Trace an account difference to independently identified postings and source records. Use when equal amounts are being matched without transaction evidence.
test-aggregate-trend-for-subgroup-reversal
Challenge an aggregate trend by checking comparable subgroup rates and changing group weights. Use when the total moves opposite to every subgroup.
challenge-a-survey-instrument-for-contamination
Review draft survey questions, options, and order for wording that prevents the intended construct from being measured clearly.
contrast-described-and-observed-workflows
Compare an approved internal workflow with consented case observations to expose actual variants and undocumented exception paths.
establish-milestone-readiness-from-evidence
Check a project milestone's predecessors and required acceptance artifacts before reporting it ready or complete.
explain-a-service-charge-from-effective-rules
Reconstruct a proposed service charge from supplied price rules, eligibility, effective time, quantity, and rounding.
propagate-a-plan-change-through-commitments
Trace a proposed project-plan change through linked dates, resources, acceptance checks, and handoffs before an owner decides on it.
test-control-operation-on-a-bounded-sample
Separate a stated transaction control's design from evidence that it actually operated on an authorized sample.
verify-resolution-against-original-symptom
Compare a proposed support resolution with the customer's original failing path and authorized after-change observations.
check-prerequisite-order-in-a-task-guide
Check that an ordered task guide supplies every prerequisite before its first use and has a defined stop or recovery path. Use before a reader follows procedural documentation.
define-a-user-operation-performance-envelope
Define a testable latency, throughput, reliability, and resource envelope for one user operation. Use before claiming an application is fast enough in production.
derive-state-transition-tests-from-a-contract
Derive positive, forbidden, repeated-event, and interrupted-transition tests from an explicit state contract. Use when an application has lifecycle states and events.
map-system-output-to-permitted-consumers
Map each output field to its authorized consumers, purpose, retention, and disclosure boundary. Use before proposing a new feed, report, or event stream.
classify-ambiguous-posting-account
Propose an account classification for a transaction using the supplied chart and transaction purpose. Use when a plausible amount fits several accounts.
map-repair-support-requirements-to-assets
Map a supported repair procedure to required parts, tools and test assets. Use when a repair plan may omit a prerequisite or count an unqualified substitute.
trace-statement-line-to-ledger
Trace one financial-statement line through a supplied mapping to ledger balances and adjustments. Use when a reported total lacks explainable lineage.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.