Individual skill
data-chatbots
Design and implement AI copilots that analyze structured data and propose mutations for human approval (draft → apply), not direct writes. Covers prompting, multistep compound requests (remove + add in one turn), FIFO client queuing for long agent loops, validation, session memory, optimistic versioning UX, copilot panel/surface ergonomics (floating-dockable panel, summon-hotkey size state machine), LLM tracing/observability (OpenInference + OTLP session.id grouping, orphan-span fixes, human thumbs up/down feedback annotations), and test matrices. Use when building scheduling/admin chatbots, proposal workflows, human-in-the-loop agents, or reviewing aiebot-style features.
data-chatbots/SKILL.md
Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 197
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- design Derived category
- data Derived category
- testing Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 54,489 bytesSKILL.mdcore · 54,489 bytesSKILL.mdcore · 54,489 bytesSKILL.mdcore · 54,489 bytesSKILL.mdcore · 54,489 bytesaudit-log.mddoc · 6,373 bytesemail-surface.mddoc · 13,380 bytesobservability.mddoc · 12,644 bytessamples/README.mddoc · 1,841 bytessamples/client-request-queue.tsruns · 3,870 bytessamples/orchestration-dry-run-and-query.tsruns · 6,006 bytessamples/proposal-validate-and-normalize.tsruns · 4,264 bytessamples/session-memory-with-outcomes.tsruns · 3,094 bytessamples/surface-panel-sizing.tsxruns · 11,475 bytessamples/version-stale-ux.tsruns · 3,380 bytessurface-ux.mddoc · 9,250 bytestest-cases.mddoc · 16,602 bytestiered-operation-harness.mddoc · 8,153 bytes
Read excerpt
# Data chatbots
Copilots over **authoritative structured state** (schedules, CRMs, configs) should **draft** changes and **apply** only after explicit human approval. Treat the model as a planner, not a writer.
Apply this guidance to the requested copilot surface and the data risks it
creates. Draft-before-apply, apply-equals-review, authorization, and prevention
of silent destructive replacement are invariants when the workflow can mutate
authoritative data. The remaining incidents, layers, telemetry, caching, email,
and advanced harness patterns are risk-triggered guidance or opportunities, not
a mandate to implement the entire platform. Stop when the requested workflow is
correctly proposed/applied and focused tests cover its plausible integrity
failure; report unrelated hardening as follow-up.
## Battle scars (select those matching the touched risk)