agentsclimarketplace
Sign in

Exampleboard card workflow

Skill samuelstefancic/ContextRift/examples/synthetic-project/.agents/skills/exampleboard-card-workflow

Guide changes and audits of ExampleBoard card lifecycle transitions, guards, event history, idempotent replay, and lifecycle regression tests. Use for work whose expected behavior depends on docs/card-lifecycle.md. Do not use for copy edits, formatting, generic quality checks, unrelated unit tests, or inventing missing business rules.From its SKILL.md

Install
npx -y skills add samuelstefancic/ContextRift --skill exampleboard-card-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 270 tokens by cl100k_base, as published. Nobody here has run it

ExampleBoard card workflow

Own the method for lifecycle work; keep every business oracle in the lifecycle contract.

Workflow

  1. Prove the ExampleBoard root and planned mutation paths. Stop on a wrong or ambiguous root.
  2. Read AGENTS.md and docs/card-lifecycle.md. Treat the document as the rule owner.
  3. Express each behavior as initial state, action, persisted state, event effect, and forbidden effect.
  4. Build positive, negative, and replay cases before changing an implementation or test.
  5. Use only identifiers prefixed synthetic- and domains under .test or .invalid.
  6. Make the smallest lifecycle-scoped change. Never add a transition absent from the contract.
  7. Verify state and event history. A successful response status alone does not prove behavior.
  8. Report changed artifacts, observed verification, remaining gaps, and a terminal state.

Boundaries

  • The lifecycle contract owns states, transitions, and side effects.
  • General verification tooling owns repository-wide quality gates.
  • This skill does not authorize network access, external delivery, or durable memory writes.
  • Missing or contradictory lifecycle rules produce PROVEN_BLOCKED.
  • Verification requiring an unavailable human-visible tool produces AWAITING_USER_VERIFICATION.
  • Only current, observed evidence can produce SUCCESS.

What ships with it: 1 file

256 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.