filescom-expectations SKILL.md skillA
filescom-expectations from files-com/files-cli is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add files-com/files-cli/filescom-expectations@git:20260924.4e0e2bcPins git:20260924.4e0e2bc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- files-com/files-cli
- Path
skills/filescom-expectations/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260924.4e0e2bc, committed Sep 24, 2026
- First version recorded
- Jun 4, 2026
- Size
- 10,813 bytes
- Repository stars
- 46
- License
- MIT
Expectations let your Files.com site define what “correct” file delivery looks like, continuously evaluate whether it happened, and keep history when it did not.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# filescom-expectations Expectations let your Files.com site define what “correct” file delivery looks like, continuously evaluate whether it happened, and keep history when it did not. Expectations are meant to answer operational questions like: * Did the expected file arrive? * Was it on time? * Did it meet the required shape and count rules? * Is there an active issue someone needs to acknowledge? Expectations are different from Automations and Syncs. Automations and Syncs act on files; Expectations monitor whether expected files arrived on time, in the right place, and in the right shape. In practice, Expectations are the sensor and Automations are the actuator. An Expectation combines four concepts: 1. **Scope**: where to look for candidate files, using `path`, `source`, and optional `exclude_pattern`. 2. **Trigger / timing**: when a window opens and how long it stays eligible, using `trigger`, schedule fields, `lookback_interval`, `late_acceptance_interval`, `inactivity_interval`, and `max_open_interval`. 3. **Criteria**: what must be true for the window to succeed, using the structured `criteria` JSON document. …
Read the whole file at its exact version.
How to install
mdr add files-com/files-cli/filescom-expectations@sha256:38fffdec036a615fThe line at the top of this page pins the label git:20260924.4e0e2bc, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_of6uqk6oyhz7c2wq)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 4, 2026 and Sep 24, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.4e0e2bc latest | 2026-09-24 | 4e0e2bc | 10,813 B | A | view · diff |
| git:20260810.0a28bac | 2026-08-10 | 0a28bac | 10,820 B | A | view · diff |
| git:20260806.a70eeb9 | 2026-08-06 | a70eeb9 | 10,489 B | A | view · diff |
| git:20260715.2277f35 | 2026-07-15 | 2277f35 | 10,244 B | A | view · diff |
| git:20260604.f117d9f | 2026-06-04 | f117d9f | 9,314 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10813 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
files-com/files-cli · 46 stars · license MIT · pushed 2026-11-06 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_of6uqk6oyhz7c2wq GET https://markdownregistry.com/api/v1/resolve?ref=files-com/files-cli/filescom-expectations GET https://markdownregistry.com/api/v1/blob/38fffdec036a615f354ea4a32bac284ea2036f071132425830f998d0dba3d083
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.