AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Scan Releases

skill-onewave-ai-open-agent-stack-scan-releases · by OneWave-AI

Scan official AI release notes, changelogs, and deprecation pages, then flag what affects the user's stack and recommend an action for each item. Trigger on requests like "what AI releases happened recently," "check if my models or tools are deprecated," "any changelog updates that affect my stack," or periodic release sweeps.

↗ Website ↗ Repository
— No reviews yet
0 installs
31 views
0.0% view→install

Install

$ agentstack add skill-onewave-ai-open-agent-stack-scan-releases

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-onewave-ai-open-agent-stack-scan-releases)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Scan Releases? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Scan Releases

Find recent AI model and tool activity, then report only what matters to the user's stack. This skill needs live web access; use the built-in web tool. No API key is required.

Workflow

  1. Establish the stack. Ask the user which models, APIs, SDKs, and tools they depend on, or infer from the project (package manifests, config files, env var names). Record exact names and current versions.
  2. Establish the time window. Default to the last 14 days unless the user gives a date or range. Note the cutoff date explicitly.
  3. Build the source list. For each stack item, identify its official release notes, changelog, and deprecation or end-of-life page. See references/sources.md for canonical URLs by vendor and how to find missing ones.
  4. Fetch each source with the web tool. Read the actual pages; do not rely on memory or summaries. Capture version, date, and the concrete change for every entry inside the window.
  5. Classify each entry as Release, Change, or Deprecation. Drop entries older than the cutoff. Discard marketing items with no behavioral or version impact.
  6. Flag stack impact. Mark every entry that touches a declared stack item. For each flagged item, assign severity using references/impact-rubric.md (breaking, behavioral, additive, informational).
  7. Recommend an action per flagged item: migrate now, plan migration before a stated cutoff, adopt optionally, or no action. Include the deprecation deadline when one exists.
  8. Verify before reporting. Confirm each claim against its source URL, dates are within the window, and version strings are exact. Drop anything you cannot source.
  9. Report using the format in references/report-format.md: a short stack-impact section first (sorted by severity), then a brief other-activity section. Cite the source URL for every item.

Rules

  • Source every claim with a live URL. No unsourced or remembered releases.
  • Lead with what affects the user. Keep non-impacting activity to one line each.
  • State exact versions, dates, and deprecation deadlines. Avoid vague terms like "recently."

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML