How do I install the Faasjs Specs skill?

Run npx skillmds@latest add faasjs/faasjs-specs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Faasjs Specs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Faasjs Specs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Faasjs Specs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Faasjs Specs?

faasjs (@faasjs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Faasjs Specs by faasjs — Agent Skill

Name: Faasjs Specs
Rating: 4.666666666666667 (3 reviews)
Author: faasjs

Faasjs Specs

Use when implementing, reviewing, or verifying normative FaasJS runtime behavior and compatibility for faas.yaml, staged config discovery and merge order, zero-mapping route resolution, HTTP request/response protocol envelopes, status behavior, plugin identity, concurrent mount and failed-mount retry behavior, lifecycle execution, config layering, and config-driven plugin loading.

faasjs dba14a3 5 files · 20.4 KB Updated Sep 10, 2026

File contents

FaasJS Specifications

Default Workflow

Load the relevant spec before changing runtime behavior or public documentation.
Treat MUST/SHOULD/MAY language as normative.
Keep implementation, docs, and tests aligned with the spec.
Preserve backwards compatibility unless the change is intentionally breaking and documented.

Load These References

faas.yaml placement, discovery, merge order, staging keys, server node, plugins node, and YAML subset: references/specs/faas-yaml.md.
Zero-mapping file naming and route lookup order: references/specs/routing-mapping.md.
HTTP request, response envelope, status, and transport behavior: references/specs/http-protocol.md.
Plugin identity, lifecycle execution, config layering, manual registration, and config-driven loading: references/specs/plugin.md.

Gotchas

Specs are normative and may be stricter than general guides.
Route behavior and config merge order are compatibility-sensitive.
HTTP response behavior must preserve envelope and low-level error distinctions.
Plugin config precedence must stay aligned with both manual and config-driven loading.

Validation

Run targeted runtime tests for the spec area changed.
Run npm run doc after spec source edits.
Run cd docs && npm run build when docs routing, spec pages, or links change.

Frequently asked questions