agentsclimarketplace
Sign in

Designing data model

Skill casioreview20-glitch/forge-os/skills-v2/l1/architecture/designing-data-model

Use when designing data model within architecture lifecycle boundaries, especially when does the artifact make the owned decision for designing data model explicit and bounded?.From its SKILL.md

Install
npx -y skills add casioreview20-glitch/forge-os --skill designing-data-model

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

  • 14 days oldThe repository was created 14 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.
  • 11 stars11 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.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

0.9 KB, 86 tokens by cl100k_base, as published. Nobody here has run it

Designing Data Model

Core principle

Designing data model within architecture lifecycle boundaries. Deterministic checks own scope, typed preconditions, evidence, and coverage; the agent performs only the domain judgment that cannot be encoded safely.

Do not activate when

  • the requested outcome does not require designing data model within architecture lifecycle boundaries
  • the typed inputs for designing-data-model are absent and another technique owns the outcome

What ships with it: 9 files

13.1 KB alongside SKILL.md

evaluators/

sections/

Gives 0 of the 12 instructions most data backend skills give in 86 tokens

Counted across 229 of the 229 authors here whose files we hold, read 2026-08-07

  • Separate business logic into service layersin 22 of 229, across 15 files
  • Retry failures with exponential backoffin 21 of 229, across 14 files
  • Select only needed database columnsin 20 of 229, across 13 files
  • Abstract data access into repository classesin 19 of 229, across 12 files
  • Use centralized error handlersin 17 of 229, across 10 files
  • Use AsNoTracking for read-only queriesin 16 of 229, across 4 files
  • Use async/await for all I/O operationsin 16 of 229, across 5 files
  • Implement structured loggingin 15 of 229, across 4 files
  • Use dependency injection for all servicesin 14 of 229, across 2 files
  • Use resource-based URLs for REST APIsin 13 of 229, across 7 files
  • Invalidate cache after data changesin 13 of 229, across 9 files
  • Use a dependency injection containerin 12 of 229, across 4 files

Said here and by no other author read

  • design data model within architecture lifecycle boundaries
  • use deterministic checks to own scope
  • use typed preconditions
  • require evidence
  • require coverage
  • perform only unencodable domain judgment

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,970. 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.