agentleFS
Sign inStart free
arslanvuzmalarslanvuzmal/VoxCircuit/.agents/skills/demo-data-integrity/SKILL.md

demo-data-integrity

Skill2 starsChanged 3 months agoMITView on GitHub

Manages deterministic demo data seeding, fictional business scenarios, lead qualification scripts, and privacy masking for VoxDesk AI.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use when seeding the database (npm run demo:seed), resetting demo state (npm run demo:reset), or running demo scenario scripts (npm run …

    line 10
  2. Distinctive:

    Verify demo business profiles, agents (Maya - Reception, Alex - Lead Qual), calendar slots, and call history are fully deterministic.

    line 21
  3. Distinctive:

    Verify clear UI banner: "Fictional demonstration workspace".

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Demo Data Integrity Skill

When to Use

Use when seeding the database (npm run demo:seed), resetting demo state (npm run demo:reset), or running demo scenario scripts (npm run demo:call, npm run demo:story).

Inputs Required

  • Demo seed datasets ("Northstar Legal Consultations", fictional callers Sarah Miller, Daniel Brooks, Priya Shah).
  • Target workspace environment.

Step-by-Step Process

  1. Inspect demo data definitions in lib/demo/ and prisma/seed/.
  2. Confirm zero real personal phone numbers, emails, or client records exist in seeds.
  3. Verify demo business profiles, agents (Maya - Reception, Alex - Lead Qual), calendar slots, and call history are fully deterministic.
  4. Execute npm run demo:seed to verify seeding completes without errors.
  5. Verify clear UI banner: "Fictional demonstration workspace".

Decision Tree

  • Does seed data contain real phone numbers or emails?
    • YES -> BLOCK SEED -> Replace with fictional @example.com / +1555... numbers.
    • NO -> Execute seed script.

Validation Checklist

  • 22+ deterministic demo scenarios seeded.
  • Demo Mode operates 100% without paid API keys.
  • Reset and verify scripts execute cleanly.

Failure Conditions

  • Hardcoded real customer data or non-deterministic demo failures.

Expected Output

Seeded database with verified demo scenarios and zero privacy exposures.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free