analyzing-releases SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
analyzing-releases from buildinternet/releases is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add buildinternet/releases/analyzing-releases@git:20261008.331f43cPins git:20261008.331f43c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- buildinternet/releases
- Path
plugins/claude/releases/skills/analyzing-releases/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261008.331f43c, committed Oct 8, 2026
- First version recorded
- Apr 24, 2026
- Size
- 5,406 bytes
- Repository stars
- 13
- License
- Apache-2.0
Analyze release trends across multiple companies to produce competitive intelligence. Use when asked to compare companies, analyze a market segment, identify industry trends, forecast upcoming releases, or answer questions like "what is X shipping lately" or "how does X compare to Y." Also triggers on requests for competitive landscape analysis, feature gap analysis, or release velocity comparisons.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Analyzing Releases Turn changelog data into competitive intelligence by analyzing release patterns across a cohort of related companies. This is a **reader** workflow — it uses only the public, unauthenticated tools. There is no AI summarize/compare tool on the hosted MCP and no `summary`/`compare` command in the CLI; you fetch the raw release data and synthesize the analysis yourself. ## Tools for each step | Operation | CLI (reader) | MCP tool | |-----------|--------------|----------| | Find what's indexed for a company | `releases search <company> --json` | `search` (with `type: ["orgs","catalog"]`) | | List a company's sources | `releases list --query <company> --json` | `list_catalog` (scope with `organization`) | | Latest releases (source or org) | `releases tail <slug> --json` · `releases tail --org <org> --json` | `get_latest_releases` (`organization` / `product`, `since`/`until`) | | Keyword/semantic release search | `releases search <query> --json` | `search` with `type: ["releases"]` | | Read one release in full | `releases get <rel_id> --json` | `get_release` | …
Read the whole file at its exact version.
How to install
mdr add buildinternet/releases/analyzing-releases@sha256:eec73687fd7576efThe line at the top of this page pins the label git:20261008.331f43c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_i4xgcmslfmuu4dmc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 24, 2026 and Oct 8, 2026, about one every 56 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.331f43c latest | 2026-10-08 | 331f43c | 5,406 B | A | view · diff |
| git:20260519.8b2c986 | 2026-05-19 | 8b2c986 | 5,531 B | A | view · diff |
| git:20260424.d324276 | 2026-04-24 | d324276 | 5,379 B | A | view · diff |
| git:20260424.928779a | 2026-04-24 | 928779a | 5,173 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5406 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
buildinternet/releases · 13 stars · license Apache-2.0 · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_i4xgcmslfmuu4dmc GET https://markdownregistry.com/api/v1/resolve?ref=buildinternet/releases/analyzing-releases GET https://markdownregistry.com/api/v1/blob/eec73687fd7576ef00f2d9fa166716e3782354d5c7a15f18a32b1b130453804b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from buildinternet/releases
Every file in buildinternet/releases