Skills api-spectral
๐Ÿ“ฆ

api-spectral

v0.1.0 Content revision r2 Critical โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access๐Ÿ”‘ Env variablesโšก Contains scripts

Validate API Specifications with Spectral

Inconsistent API definitions can hide security and governance defects. This skill guides Spectral configuration, OWASP-focused linting, custom rules, reporting, and CI integration.

Supports: Claude Codex Code(CC)
โš ๏ธ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "api-spectral" from https://skillstore.io/skills/agentsecops-api-spectral.md and its manifest at https://skillstore.io/api/skills/agentsecops-api-spectral/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.

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 "api-spectral". Review an OpenAPI specification for missing authentication and insecure servers.

Expected outcome:

  • High: Three operations do not declare a security requirement.
  • High: The production server uses HTTP instead of HTTPS.
  • Next step: Add the shared security scheme, apply it globally, and rerun Spectral.

Using "api-spectral". Summarize a Spectral report for an application security review.

Expected outcome:

The report contains two errors and five warnings. Authentication and transport findings should block release; documentation warnings can enter the backlog.

Using "api-spectral". Plan CI enforcement for a large API portfolio.

Expected outcome:

  • Phase one reports errors and warnings without blocking.
  • Phase two blocks new error-level findings and records approved exceptions.
  • Phase three pins the ruleset and enforces the same policy across repositories.

Security Audit

Critical
v9 โ€ข 7/23/2026 Open versioned report

Most alerts are false positives caused by Markdown, defensive examples, fixed local file reads, or reference URLs. Confirmed risks include unverified remote downloads, mutable CI dependencies, token exposure, and fail-open scanner steps. These supply-chain and enforcement weaknesses require remediation before publication.

10
Files scanned
3,749
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (3)

Critical
Pipe to shell pattern
curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash
The template pipes an unverified installer from a mutable upstream branch directly into bash. This creates a direct supply-chain remote code execution path in CI.
High
Unpinned CI dependencies execute mutable upstream code
The templates install unversioned packages and run actions from mutable tags, including a master branch. Upstream compromise can change code executed by CI.
The files directly show unversioned package installation, mutable action tags, and aquasecurity/trivy-action@master in executable workflow steps.
High
Security pipeline can pass after scanner failures
Several scanner commands suppress failures, while later checks omit or only warn on some results. Tool errors and detected vulnerabilities can leave the workflow successful.
The templates explicitly use continue-on-error or || true, and the npm audit output is not included in the dependency failure check.
Capability review items (4)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Critical
Hardcoded URL
curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash
The mutable upstream URL supplies an installer directly to bash on the same line. A compromised branch or connection can produce arbitrary CI code execution.
High
Git platform tokens
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
The workflow gives GITHUB_TOKEN to a third-party action referenced by a mutable version tag. Compromise of that action could misuse the workflow's repository permissions.
High
Hardcoded URL
https://raw.githubusercontent.com/SecOpsAgentKit/skills/main/appsec/api-spectral/scripts/parse_spect
The workflow downloads a Python script from a mutable main branch and executes it on line 70 without a digest or signature check. Upstream compromise would execute in CI.
High
Hardcoded URL
https://raw.githubusercontent.com/SecOpsAgentKit/skills/main/appsec/api-spectral/assets/spectral-owa
The workflow downloads a Spectral ruleset from a mutable main branch and immediately consumes it. Malicious upstream changes could alter validation or load unsafe rule behavior.

Risk Factors

โš™๏ธ External commands (50)
๐ŸŒ Network access (25)
๐Ÿ“ Filesystem access (9)
๐Ÿ”‘ Env variables (23)
โšก Contains scripts (2)

Detected Patterns

Pipe to shell pattern
Audited by: codex View Audit History โ†’
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/agentsecops-api-spectral/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/agentsecops-api-spectral/security.svg)](https://skillstore.io/skills/agentsecops-api-spectral?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/agentsecops-api-spectral?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentsecops-api-spectral/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/agentsecops-api-spectral.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

AgentSecOps. (2026). api-spectral security audit report (audit version 9) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/agentsecops-api-spectral/audits/9

BibTeX citation

@techreport{agentsecops-agentsecops-api-spectral-2026, author = {AgentSecOps}, title = {api-spectral security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/agentsecops-api-spectral/audits/9}, note = {Author version 0.1.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "api-spectral security audit report (audit version 9)" version: "0.1.0" type: report authors: - name: "AgentSecOps" date-released: "2026-07-23" url: "https://skillstore.io/skills/agentsecops-api-spectral/audits/9" identifiers: - type: other value: "skillstore:agentsecops-api-spectral:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
59
Architecture
100
Maintainability
87
Content
74
Community
91
Spec Compliance

What You Can Build

Review an API specification

Find missing security schemes, insecure servers, exposed data patterns, and incomplete responses before implementation.

Create governance rules

Define organization-specific Spectral checks and map findings to OWASP API Security categories.

Add CI enforcement

Integrate specification linting, reports, artifacts, and severity thresholds into pull-request workflows.

Try These Prompts

Lint one specification
Review [SPEC_PATH] with Spectral. Identify the correct base ruleset, run linting, and summarize security findings with locations and fixes.
Build a security ruleset
Create a Spectral ruleset for [API_TYPE]. Enforce HTTPS, authentication, safe parameters, standard errors, and [ORGANIZATION_REQUIREMENT]. Explain each rule.
Triage lint findings
Analyze the Spectral report at [REPORT_PATH]. Group findings by OWASP API category, remove false positives, prioritize fixes, and define verification steps.
Design portfolio enforcement
Design a CI policy for specifications under [SPEC_DIRECTORY]. Include pinned dependencies, immutable rules, failure handling, reports, exceptions, and phased severity enforcement.

Best Practices

  • Pin Spectral, actions, rulesets, and downloaded tools to reviewed immutable versions.
  • Start with built-in rules, then add focused organizational checks with test fixtures.
  • Review findings manually and document justified exceptions with owners and expiration dates.

Avoid

  • Do not pipe remote installers into a shell or execute mutable downloaded scripts.
  • Do not suppress scanner failures without distinguishing tool errors from acceptable findings.
  • Do not treat specification linting as proof that runtime authentication and authorization are secure.

Frequently Asked Questions

Which specification formats are supported?
The guidance covers OpenAPI, AsyncAPI, and Arazzo through Spectral rulesets.
Does this skill test a running API?
No. It analyzes API definition files and related governance rules.
Can it create custom Spectral rules?
Yes. It explains JSONPath targets, built-in functions, custom functions, messages, and severity configuration.
Can it run in continuous integration?
Yes. It includes workflow templates, but remote dependencies must be pinned before production use.
Does every finding represent a vulnerability?
No. Spectral findings require context, false-positive review, and alignment with organizational policy.
What tools are required?
Node.js, npm, and Spectral are primary requirements. Individual examples may also use Git, Docker, jq, or Python.

Developer Details

License

MIT

Author version

v0.1.0

Skillstore revision

r2

Ref

9e952417e76879bc9d853e1b8b2cd6d6d8d4a1c2

Maintenance freshness

7/24/2026

Usage

4 downloads ยท 463 views

File structure

๐Ÿ“ assets/

๐Ÿ“„ .gitkeep

๐Ÿ“„ ci-config-template.yml

๐Ÿ“„ github-actions-template.yml

๐Ÿ“„ rule-template.yaml

๐Ÿ“„ spectral-owasp.yaml

๐Ÿ“ references/

๐Ÿ“„ custom_rules_guide.md

๐Ÿ“„ EXAMPLE.md

๐Ÿ“„ owasp_api_mappings.md

๐Ÿ“„ WORKFLOW_CHECKLIST.md

๐Ÿ“„ SKILL.md

More from AgentSecOps

View all
View all