agentsclimarketplace

Engifoundry

Skill caoyuan-fire/engi-foundry-skill/skills/engifoundry

EngiFoundry / engifoundry: Engineering Foundry Skill for structured AI-assisted engineering workflows

Install
npx -y skills add caoyuan-fire/engi-foundry-skill --skill engifoundry

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

One thing to look at

  • 2 stars2 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 author says it does

Copied from the file, not written here

MUST be loaded at the start of every session. Check only ./engifoundry.config.json at the project root: if it exists, load engifoundry-router; if absent, stay silent unless the user explicitly names EngiFoundry and asks to initialize it.

SKILL.md

1.8 KB, as published. Nobody here has run it

EngiFoundry Entry

Inject this entry once at the start of every session. Apply its rules to every user turn.

  1. At session start, check exactly <project-root>/engifoundry.config.json once. Do not search for it.
  2. If it exists, read engifoundry-router/SKILL.md in full before responding to the user.
  3. If it does not exist, remain uninitialized and load engifoundry-init/SKILL.md only when both conditions are true:
    • The request contains $engifoundry, engifoundry, engi, or foundry as an explicit, case-insensitive identifier.
    • The request semantically asks to initialize, scaffold, create, onboard, connect, migrate, or upgrade the project for EngiFoundry.
  4. Otherwise bypass EngiFoundry silently and handle the request normally.
  5. After Init completes, check exactly <project-root>/engifoundry.config.json once again. If it now exists, immediately read engifoundry-router/SKILL.md in full. Do not require a new session.

Reading only Router metadata or a summary is forbidden. The Router governs every user turn after it is loaded.

Initialization matching is semantic, not a fixed command. Initialization language without an explicit EngiFoundry identifier must never activate EngiFoundry.

Never scan for configuration. Never recognize any other filename, location, or project signal. Do not validate configuration content or project records; Init and Node skills own those rules.

Do nothing else. Never route, infer, govern, plan, execute, verify, deliver, or load Node skills from this entry.

Keep looking

Skills are one crate of 328,083. 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.