Skip to content
Skills Library
Programming · Review & audit

np-engineering-api-contract

/np-engineering-api-contract

Review an integration API contract. Use when a team needs predictable interfaces and failure handling.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Review an integration API contract. Use when a team needs predictable interfaces and failure handling.

Original author description

Review an integration API contract. Use when a team needs predictable interfaces and failure handling.

How it works

  1. Inputs and task
  2. Deliverable and acceptance
  3. Reference starting points
  4. Execution boundary
Original SKILL.md headings · 35 lines, 450 words
SKILL.md preview
---
name: np-engineering-api-contract
description: "Review an integration API contract. Use when a team needs predictable interfaces and failure handling."
metadata:
  version: "0.4.0"
  license: MIT
---

# Review an integration API contract

Complete this specific task for a technology organization or research project in Nepal. Agree the actual organization, locality, systems, reference period and decision owner before drawing conclusions. Scale the work to the case; do not impose enterprise infrastructure on a small shop.

## Inputs and task

Obtain: Current endpoint/schema documentation, authorized test environment and data ownership. Start from available evidence and identify missing inputs explicitly; request only what materially blocks the decision. Use role identifiers and redacted extracts rather than unnecessary customer, student or account data.

1. Specify identity, payload, version and error semantics.
2. Test valid, rejected, duplicate and retried requests within scope.
3. Record reconciliation and compatibility gaps.

Use [the blank working record](assets/working-record.csv) as a starting point. Adapt fields to the case while preserving source references and unknowns. Add an evidence register with source URL/file, exact page/row/test locator, observation date, period, geography and limitations. Preserve BS/AD calendar labels and original units when relevant; document conversions.

## Deliverable and acceptance

Return the completed working record plus a short decision note: scope, established findings, unknowns, next actions, responsible role, due date and verification method. Empty cells are not evidence. Mark absent evidence UNKNOWN and ambiguous interpretations REVIEW_REQUIRED. Separate observed facts, assumptions and recommendations. Never fill an example template with fabricated business facts.

Acceptance: **A successful happy-path request is not treated as complete integration acceptance.**

If acceptance cannot be demonstrated, deliver a provisional result and the specific missing evidence or test; do not label the task passed. Regulatory interpretations require current owning documents and applicable amendments. A policy date or technical manual alone does not establish current Nepal compliance. Seek an authorized domain reviewer where the decision requires one.

## Reference starting points

Select references that actually govern the case. Retrieve and inspect the relevant passage before citing a claim; these links are discovery aids, not prevalidated conclusions. Technical documents apply only if the corresponding product/version is actually used; they are not evidence of Nepal market demand. Search the official source again if a link moves.

- [HTTP response status codes; use for the actual HTTP API contract](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status) — Mozilla Contributors / MDN; CURATED_STARTING_POINT_REQUIRES_PASSAGE_AND_APPLICABILITY_REVIEW.

## Execution boundary

This skill prepares and reviews the task artifact. Obtain explicit authorization before public posting, external messages, bid submission, pricing commitments or production changes. Use approved test environments for intrusive checks. Never put secrets or unredacted private records in a public repository. Preserve existing work and provide recovery steps for authorized changes.

Original Dharma OS authored workflow · MIT · 0.4.0. This folder is self-contained; it does not require other Dharma OS skills, an API key or proprietary tools. Live research uses the tools available in the user's environment.
Files in this package (2)
  • SKILL.md 4 KB
  • assets/working-record.csv 1 KB

Versions

The database has no other skills named np-engineering-api-contract.

Database snapshot: 13.11.2026 · package version 01cd422dbc39 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90api-contract-review
    Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).
  • 90api-design
    Contract-first API design for stable, evolvable interfaces. Use whenever defining a new API endpoint, inter-service boundary, or modifying an existing contract. Includes backward compatibility checklist and error contract specification.
  • 100audit-fe-api
    Audit frontend API calls against backend implementation for contract alignment and network shape. Use when "API audit", "FE-BE contract", or "review frontend API integration". Live 4xx/5xx reproduction → debug-fe-be-integration.
  • 90code-audit
    Review code for correctness bugs, concurrency and lifecycle errors, type-safety holes, error handling gaps, API-contract breaks, and maintainability problems, with every finding gated on a concrete failure scenario. Use when asked to review code, check a diff or branch for bugs,…
  • 100api-contract-testing
    Design and review API contract tests across providers and consumers. Use for schema changes, compatibility regressions and client integration failures.
  • 96error-handling
    统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.