generate-api-client
Generate Type-Safe API Clients
Manual API client updates drift when OpenAPI contracts change. This skill guides Orval generation and type checking so frontend clients stay aligned.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "generate-api-client" from https://skillstore.io/skills/crearize-generate-api-client.md and its manifest at https://skillstore.io/api/skills/crearize-generate-api-client/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "generate-api-client". Generate the frontend client from the current OpenAPI spec.
Expected outcome:
The skill confirms the spec path, runs Orval, checks generated API and model files, and reports type-check status.
Using "generate-api-client". Regenerate the API client after a backend endpoint changed.
Expected outcome:
The skill updates the generated client from the latest contract and summarizes whether TypeScript validation passed.
Using "generate-api-client". Find out why API client generation is failing.
Expected outcome:
The skill separates spec lookup, generation, file verification, and type checking so the failing phase is clear.
Security Audit
SafeMost static detections are false positives caused by markdown code fences and read-only ls examples. Two command blocks are confirmed medium-risk because they run pnpm and npx project tooling in a community repository. No prompt injection, data exfiltration intent, or hidden authority claims were found in SKILL.md.
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (9)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/crearize-generate-api-client/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/crearize-generate-api-client?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/crearize-generate-api-client?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crearize-generate-api-client/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/crearize-generate-api-client.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Crearize. (2026). generate-api-client security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crearize-generate-api-client/audits/10BibTeX citation
@techreport{crearize-crearize-generate-api-client-2026,
author = {Crearize},
title = {generate-api-client security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/crearize-generate-api-client/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "generate-api-client security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "Crearize"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/crearize-generate-api-client/audits/10"
identifiers:
- type: other
value: "skillstore:crearize-generate-api-client:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Refresh frontend clients after backend changes
Regenerate the TypeScript API client after the OpenAPI contract changes, then confirm the generated files and types.
Keep full-stack contracts aligned
Use one guided flow to verify the backend specification and update the frontend client in the same workspace.
Standardize generated client reviews
Apply a repeatable checklist for API client generation before merging contract or frontend integration changes.
Try These Prompts
Use generate-api-client to confirm the OpenAPI file exists, run the configured Orval generation, and report the generated files.
Use generate-api-client after the backend OpenAPI spec changed. Verify generation, run type checking, and summarize any changed client outputs.
Use generate-api-client to regenerate the API client, confirm the expected generated files, and tell me whether TypeScript type checking passes.
Use generate-api-client to run the flow phase by phase. Identify the failing phase and recommend the smallest project change to fix it.
Best Practices
- Review OpenAPI changes before regenerating the client.
- Inspect project package scripts before running generation in an untrusted repository.
- Commit generated client changes with the related backend contract change when the repository expects generated files.
Avoid
- Editing generated API client files by hand instead of changing the OpenAPI spec or Orval configuration.
- Running generation before dependencies and package scripts are reviewed.
- Ignoring TypeScript errors after generation.