seo-reporting SKILL.md skillA
seo-reporting from rankmyseo/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rankmyseo/skills/seo-reporting@git:20261028.2898becPins git:20261028.2898bec in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rankmyseo/skills
- Path
skills/seo-reporting/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261028.2898bec, committed Oct 28, 2026
- First version recorded
- Oct 24, 2026
- Size
- 4,128 bytes
- Repository stars
- 5
- License
- MIT
Standard formats for the change log and the owner report. The change log records every page change with its date, reason, and expected effect, so later checks have a baseline. The owner report is a short weekly or monthly summary the owner can read without SEO knowledge, and the executive summary is a one-page scorecard with the decisions a manager or client must make. Use after any change to a live site, and when writing the weekly, monthly, or executive report.
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
# Reporting Goal: every change to a live site is recorded, and the owner gets a short, consistent report each week or month. Acceptance: the owner can find any change by date, see why it was made, and read a report that says what moved, what did not, and what happens next. ## 1. The change log Keep one log per site. Add one row for each change, on the day it is made. | Date | Page or URL | What changed | Why | Expected effect | Metric to check | Check date | Result | | --- | --- | --- | --- | --- | --- | --- | --- | Rules: - One row per change. Batch edits to one page on one day can share a row. - "Why" names the evidence: the number, the issue, or the owner's request. "Looks better" is not a reason. - "Expected effect" names one metric. Do not promise a rank. - "Check date" is at least two weekly checks after the change, or four weeks of Search Console data, whichever is later. - "Result" stays blank until the check date. Then write what happened, with the number and its source. - Record owner-made changes too, such as a new page the owner published or a setting they changed. ## 2. The weekly owner report Keep it under one page. Use this order: …
Read the whole file at its exact version.
How to install
mdr add rankmyseo/skills/seo-reporting@sha256:66d5c88e258e5f31The line at the top of this page pins the label git:20261028.2898bec, 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_ligmh6stmejhvyil)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 24, 2026 and Oct 28, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.2898bec latest | 2026-10-28 | 2898bec | 4,128 B | A | view · diff |
| git:20261024.3bd54ee | 2026-10-24 | 3bd54ee | 2,859 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 (4128 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
rankmyseo/skills · 5 stars · license MIT · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ligmh6stmejhvyil GET https://markdownregistry.com/api/v1/resolve?ref=rankmyseo/skills/seo-reporting GET https://markdownregistry.com/api/v1/blob/66d5c88e258e5f31eed875d0db6a099334d0f38382d6af60f9b95ae2a1f0a3b3
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.