caldova-demo
Skill1 starsChanged 53 days agoMITView on GitHub
Use when: configuring, deploying, rehearsing, debugging or changing the Caldova staffing demo, Azure Function or demo preflight.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/frontiertour27-BRK390-building-ai-applications-with-microsoft-databases-and-fabricword for word, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 1
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- src/caldova-insights/AGENTS.mdAGENTS.md
- demo-security-reviewSkill
- caldova-campaign-planningSkill
- app-designSkill
- app-validationSkill
- dax-authoringSkill
- fabric-cliSkill
- fabric-sdkSkill
- playwright-cliSkill
- query-designSkill
- rayfin-functionsSkill
- rayfinSkill
- schema-discoverySkill
- visualsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read the Act 3 architecture and deployment instructions.
- Distinctive: line 11
Use the December staffing workflow and keep its case and evidence boundaries separate from the earlier production-review experience.
- Very specific: line 13
Keep data/scenario.json frozen.
- Very specific: line 18
Prefer managed identity. Never copy values from private .azure/ records into code.
- Very specific: line 19
Run npm test before packaging.
- Distinctive: line 23
Do not run them merely to prove local tests pass.
- Distinctive: line 26
Never replay uncertain writes.
- Distinctive: line 28
Before sharing, use demo-security-review.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Caldova Demo
Read the Act 3 architecture and deployment instructions. Work from the repo root.
- Use the December staffing workflow and keep its case and evidence boundaries separate from the earlier production-review experience.
- Keep
data/scenario.jsonfrozen. Derive staffing from its separate extension; runnpm run demo:scenario:checkafter any relevant change. - Diagnose with the owning handler, a nearby regression test and sanitized telemetry. A static HTTP 200 is not dependency readiness. Do not weaken authentication.
- Require explicit subscription, tenant, Function, SQL, Cosmos and embedding settings.
Prefer managed identity. Never copy values from private
.azure/records into code. - Run
npm testbefore packaging. The package is built withnpm run demo:packageusingnpm ciand a dependency audit. - Cloud deployment, provisioning, role assignments, seed and SQL verification are mutations requiring owner authorization. Transaction rollback is still a mutation. Do not run them merely to prove local tests pass.
- The protected preflight verifies actual SQL and Cosmos reads plus quota headroom. It does not certify interactive speaker login, embeddings or paused-database resume.
- Never replay uncertain writes. Preserve request IDs, compare receipts and context hashes, and use separate case IDs for rehearsals instead of resetting approvals.
- Before sharing, use demo-security-review.
Describe fictional data, authored assumptions, calculated forecasts and observed execution accurately. A fixture is not a live run and an approval is not a hiring action.
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
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.

