Nodejs Backend Patterns
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
A skill your agent uses when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests.
Install Cross Platform Contract Propagation Audit
$ npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills cross-platform-contract-propagation-audit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cross-platform-contract-propagation-audit .claude/skills/cross-platform-contract-propagation-audit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cross-platform-contract-propagation-audit" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/cross-platform-contract-propagation-audit into .claude/skills/cross-platform-contract-propagation-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-contract-propagation-audit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/cross-platform-contract-propagation-auditType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills cross-platform-contract-propagation-audit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cross-platform-contract-propagation-audit .agents/skills/cross-platform-contract-propagation-audit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cross-platform-contract-propagation-audit" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/cross-platform-contract-propagation-audit into .agents/skills/cross-platform-contract-propagation-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-contract-propagation-audit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills cross-platform-contract-propagation-audit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cross-platform-contract-propagation-audit .cursor/skills/cross-platform-contract-propagation-audit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cross-platform-contract-propagation-audit" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/cross-platform-contract-propagation-audit into .cursor/skills/cross-platform-contract-propagation-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-contract-propagation-audit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/cross-platform-contract-propagation-audit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills cross-platform-contract-propagation-audit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cross-platform-contract-propagation-audit .gemini/skills/cross-platform-contract-propagation-audit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cross-platform-contract-propagation-audit" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/cross-platform-contract-propagation-audit into .gemini/skills/cross-platform-contract-propagation-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-contract-propagation-audit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills cross-platform-contract-propagation-auditInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cross-platform-contract-propagation-audit .github/skills/cross-platform-contract-propagation-audit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cross-platform-contract-propagation-audit" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/cross-platform-contract-propagation-audit into .github/skills/cross-platform-contract-propagation-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-contract-propagation-audit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills cross-platform-contract-propagation-audit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cross-platform-contract-propagation-audit .opencode/skills/cross-platform-contract-propagation-audit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cross-platform-contract-propagation-audit" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/cross-platform-contract-propagation-audit into .opencode/skills/cross-platform-contract-propagation-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-contract-propagation-audit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cross-platform-contract-propagation-audit- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,018 words
- Files
- 1
- Skills in repo
- 1,497
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests.
- Works in 6 steps: Write the semantic contract → Enumerate the propagation graph → Trace evidence edge by edge → …
- Auditing whether a field
- SKILL.md covers Overview, When to Use This Skill, How It Works and Example, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cross Platform Contract Propagation Audit is an agent skill from sickn33/agentic-awesome-skills. Use when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering API design. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Auditing whether a field
- API contract propagates consistently across storage
Example prompts
- “/cross-platform-contract-propagation-audit”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cross Platform Contract Propagation Audit loads about 2.3k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 1,018 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 1,018 words, ~2,270 tokens.
Download SKILL.mdSave it as
.claude/skills/cross-platform-contract-propagation-audit/SKILL.md (or your agent's skills folder).- name
- cross-platform-contract-propagation-audit
- description
- Use when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests.
- category
- development
- risk
- safe
- source
- self
- source_type
- self
- date_added
- 2026-08-18
- author
- Whxuan0701
- tags
- contract-audit, cross-platform, api, schema, feature-flags
- tools
- claude, cursor, gemini, codex
Cross-Platform Contract Propagation Audit
Overview
Audit a contract change from its source through every transformation and consumer before release. Treat a field that exists in one schema as incomplete until its meaning, defaults, wire behavior, rollout controls, client handling, analytics, and tests are proven across all relevant paths.
This is a read-only evidence workflow. It reports propagation gaps; it does not implement them.
When to Use This Skill
- Use when adding or changing a field, enum value, status, capability, or feature flag shared by multiple components.
- Use when database, backend, API, Web, Android, iOS, jobs, events, or analytics may interpret the same value differently.
- Use when a change must preserve existing records, older clients, or a default-off rollout.
- Use when a change looks complete in one endpoint but may be missing from alternate entry points or generated models.
How It Works
Step 1: Write the semantic contract
Before tracing files, state the business invariant and define every observable state. Distinguish values that languages and serializers often collapse:
| State | Questions to answer |
|---|---|
| missing | Is the property absent on the wire or in an old record? |
null | Is it unknown, inherited, unsupported, or invalid? |
false or zero | Is this an explicit disabled value or a default? |
true or non-zero | What behavior becomes available? |
| unknown enum | Must old consumers ignore, preserve, or reject it? |
Record compatibility requirements, ownership, rollout condition, and the exact user-visible or system behavior for each state. Do not accept optional, nullable, and default false as equivalent without evidence.
Step 2: Enumerate the propagation graph
List every relevant node before judging completeness:
source of truth
-> persistence and migration
-> domain model and mapper
-> service or policy computation
-> every API, event, cache, and job projection
-> generated or handwritten client model
-> client state and presentation logic
-> analytics and operational observability
-> tests, rollout, and rollback checksInclude alternate read/write endpoints, list/detail projections, background consumers, offline caches, admin surfaces, older app versions, and feature-flag evaluation points when they are in scope. Mark a node not applicable only with a reason.
Step 3: Trace evidence edge by edge
For each edge, cite the producer, transformation, consumer, and test using file paths, symbols, schema names, or other inspectable evidence. Assign one status:
| Status | Meaning |
|---|---|
proven | Producer and consumer agree, with direct evidence and relevant test coverage. |
partial | Some paths or states agree, but coverage is incomplete. |
missing | A required propagation edge or consumer is absent. |
conflict | Two layers implement different semantics. |
unknown | Evidence is unavailable or ambiguous. |
not_applicable | The layer is outside scope, with a stated reason. |
Do not upgrade likely, convention, type compatibility, or a framework default to proven. A declaration proves shape, not runtime mapping or behavior.
Step 4: Check the high-risk boundaries
Inspect these boundaries explicitly:
- Migration and existing data: default, backfill, nullability, rollback, mixed-version reads and writes.
- Domain mapping: missing/null coercion, enum fallbacks, validation, derived values, serialization symmetry.
- Fan-out surfaces: list and detail DTOs, events, caches, jobs, search indexes, SDKs, and alternate API versions.
- Client compatibility: missing and explicit-null decoding, unknown enums, generated-model drift, cached payloads, release or minified builds.
- Rollout control: flag default, evaluation location, cohort consistency, kill switch, and behavior when stored data disagrees with the flag.
- Analytics: offered, rendered, attempted, succeeded, and failed events carry enough contract and version context to join reliably.
Step 5: Build a state-by-path test matrix
Cross the semantic states from Step 1 with every material path from Step 2. At minimum, include existing-data defaults, enabled and disabled values, flag on and off, alternate endpoints, current clients, and representative older clients.
For each cell, record the expected result, evidence, and status. A unit test at one layer does not prove an end-to-end cell. Use unknown for unexecuted cells.
Show full SKILL.md (446 more words)Show less
Step 6: Decide against explicit release gates
Derive gates from the stated contract, not from intuition. A release is blocked when an edge or compatibility invariant that the contract explicitly requires is missing, conflict, or unknown, or when rollback cannot contain the new behavior. Use inconclusive only when the release contract itself is absent or ambiguous, so the audit cannot determine which edges or invariants are required. Do not downgrade a known required but unproven gate from blocked to inconclusive.
Return the smallest verification or repair set that would change the verdict. Keep implementation suggestions separate from proven findings.
Example
For a nullable can_complete field that should expose an action only when both the stored capability and server flag are true:
Invariant: show action = (feature_flag == on) AND (can_complete == true)
Path Status Evidence
DB null -> domain false -> detail API partial mapper exists; null case untested
DB true + flag off -> detail API unknown flag branch not tested
DB true + flag on -> list API missing list DTO omits field
missing field -> Web hidden proven client test covers missing
explicit null -> Android hidden unknown decoder behavior untested
impression -> click attribution missing click event lacks capability/cohort
Verdict: blocked by the missing list projection and incomplete flag enforcement;
older-client and explicit-null compatibility remain unverified.Best Practices
- Start from behavior and state semantics, then trace code; do not start from a filename guess.
- Search for field names, serialized aliases, enum values, DTOs, mappers, flags, and analytics events.
- Cite negative searches with their scope and revision; absence claims require a bounded search.
- Separate source-of-truth behavior from client presentation and telemetry.
- Verify all entry points that can produce the same user-visible state.
- Keep findings reproducible: contract, revision, evidence, status, impact, and next check.
Limitations
- Static evidence cannot prove runtime configuration, deployed schema state, generated-code freshness, or client behavior that was not exercised.
- Repository access may omit private services, analytics schemas, remote flags, or older released clients; mark those edges
unknown. - This skill finds propagation and semantic gaps, not every security, performance, or product-design defect.
- A complete graph does not prove the underlying business rule is correct.
Security & Safety Notes
- Keep the audit read-only unless the user separately authorizes implementation or runtime testing.
- Redact production records, credentials, user identifiers, and sensitive payload fields from evidence.
- Do not enable flags, mutate data, publish schemas, or exercise production actions merely to fill an evidence gap.
Common Pitfalls
- Problem: The field exists in the database and one response, so the change is called complete. Solution: Trace every projection and consumer, including alternate endpoints and events.
- Problem: Missing, null, and false are treated as the same state. Solution: Define and test each state at every serialization boundary.
- Problem: Type declarations are treated as runtime proof.
Solution: Require mapping, decoding, behavior, and test evidence before using
proven. - Problem: The feature flag hides UI but not data or alternate APIs. Solution: Map every flag evaluation point and test stored-value/flag combinations.
- Problem: A green unit test suite is presented as cross-platform coverage.
Solution: Build the state-by-path matrix and preserve unexecuted cells as
unknown.
Related Skills
@api-analyzer- Validate the correctness of an individual API request.@spec-to-code-compliance- Compare formal blockchain specifications with implementations.@technical-change-tracker- Record implementation progress and handoff state across sessions.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/cross-platform-contract-propagation-audit of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit b84d35a
Used in 1 other repository
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Cross Platform Contract Propagation Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cross Platform Contract Propagation Audit this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Nodejs Backend Patternsever-works/ever-works | 162 | 18 repos | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| API DesignerJeffallan/claude-skills | 12k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Pangolin CRUD Endpointsfosrl/pangolin | 23k | — | ~461 | Automated safety check: Pass | Custom licence | |
| Backend PatternshellangleZ/burn-in-cceverywhere-ralph | 112 | 17 repos | ~3.3k | Automated safety check: Pass | None | |
| API Design Principlesjh941213/my-cc-harness | 125 | 18 repos | ~3.4k | Automated safety check: Pass | None |
Similar skills
API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
Pangolin CRUD Endpoints
fosrl/pangolin
Use whenever asked to add, create, or scaffold a CRUD endpoint, router, or entity in this repo's server (create/list/get/update/delete handlers, new…
Backend Patterns
hellangleZ/burn-in-cceverywhere-ralph
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
API Design Principles
jh941213/my-cc-harness
REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.
API And Interface Design
dzhalaevd/Donatello
Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.
More from sickn33/agentic-awesome-skills
All 1,497 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Categories
Questions about Cross Platform Contract Propagation Audit
What does Cross Platform Contract Propagation Audit do?
A skill your agent uses when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests. Cross Platform Contract Propagation Audit is an agent skill from sickn33/agentic-awesome-skills. Use when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests.
When should I use Cross Platform Contract Propagation Audit?
Cross Platform Contract Propagation Audit fits situations like: auditing whether a field; API contract propagates consistently across storage.
How do I install Cross Platform Contract Propagation Audit in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a claude-code`. Or copy the skill folder (skills/cross-platform-contract-propagation-audit in sickn33/agentic-awesome-skills) into .claude/skills/cross-platform-contract-propagation-audit in your project. Claude Code loads it when a task matches its description.
How do I install Cross Platform Contract Propagation Audit in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a codex`. Or copy the skill folder (skills/cross-platform-contract-propagation-audit in sickn33/agentic-awesome-skills) into .agents/skills/cross-platform-contract-propagation-audit in your project. Codex loads it when a task matches its description.
Can I use Cross Platform Contract Propagation Audit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill cross-platform-contract-propagation-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-platform-contract-propagation-audit, .gemini/skills/cross-platform-contract-propagation-audit, .github/skills/cross-platform-contract-propagation-audit and .opencode/skills/cross-platform-contract-propagation-audit in your project.
What does Cross Platform Contract Propagation Audit need to run?
SKILL.md names no scripts, command-line tools or credentials: Cross Platform Contract Propagation Audit is instructions for the agent only.
Does Cross Platform Contract Propagation Audit access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cross Platform Contract Propagation Audit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cross Platform Contract Propagation Audit use?
Cross Platform Contract Propagation Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cross Platform Contract Propagation Audit use?
About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cross Platform Contract Propagation Audit?
Skills that share tags, products or a category with Cross Platform Contract Propagation Audit: Nodejs Backend Patterns (ever-works/ever-works, 162 stars), API Designer (Jeffallan/claude-skills, 12k stars), Pangolin CRUD Endpoints (fosrl/pangolin, 23k stars) and Backend Patterns (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cross Platform Contract Propagation Audit?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.