weekly-report
/weekly-report
Compile a week-over-week rank-movement report from saved checks. Use when summarizing how rankings changed over a recent window. Do not use for starting new checks or treating a current competitor snapshot as weekly history.
- Author
- corgicorner ↗
- Repository
- bisibility ↗
- Licence
- AGPL-3.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
What it does and when to use it
Compile a week-over-week rank-movement report from saved checks. Use when summarizing how rankings changed over a recent window. Do not use for starting new checks or treating a current competitor snapshot as weekly history.
Original author description
Compile a week-over-week rank-movement report from saved checks. Use when summarizing how rankings changed over a recent window. Do not use for starting new checks or treating a current competitor snapshot as weekly history.
How it works
- Prerequisites and bounds
- 1. Resolve the keyword scope
- 2. Read completed checks for one consistent window
- 3. Compare only supported observations
- 4. Add competitor context only when useful
- 5. Deliver a concise report
SKILL.md preview
---
name: weekly-report
description: Compile a week-over-week rank-movement report from saved checks. Use when summarizing how rankings changed over a recent window. Do not use for starting new checks or treating a current competitor snapshot as weekly history.
---
# Weekly rank-movement report
Summarize saved ranking changes for an agreed project and reporting window.
This workflow only reads data. It never starts checks or changes settings.
## Prerequisites and bounds
Resolve `$BISIBILITY_BASE` including `/api/v1`, a read-scoped bearer credential
in `$BISIBILITY_API_KEY`, and `$PROJECT_ID` from `GET /projects`. Never display
the credential. With a personal token, pass `X-Bisibility-Project: $PROJECT_ID`
on paths without a project ID when the target would otherwise be ambiguous.
State the window and time zone, normally the last seven days in UTC. Confirm a
bounded keyword scope before reading a large project. Lists return `data` and
`meta.next_cursor`; follow pages within that scope and disclose any truncation.
Errors use `application/problem+json`; honor 429 retry windows.
## 1. Resolve the keyword scope
If the user names a saved segment, read
`GET /projects/{project_id}/saved-views` first and inspect its supported filters.
Otherwise read `GET /projects/{project_id}/keywords` directly. Keep each keyword's
public ID, text, canonical market and device. Do not combine different targets
just because their keyword text matches.
## 2. Read completed checks for one consistent window
For each scoped keyword, request `status=completed` and ISO date-time bounds
using `since` and `until` (not from/to):
```bash
curl -fsS "$BISIBILITY_BASE/keywords/$KEYWORD_ID/rank-checks?status=completed&since=2026-10-09T00:00:00Z&until=2026-10-16T00:00:00Z&limit=100" -H "Authorization: Bearer $BISIBILITY_API_KEY" -H "X-Bisibility-Project: $PROJECT_ID"
```
Dates above are illustrative; calculate the requested window. Paginate each
keyword's history. Results are newest first. Read `checked_at`, `position`,
`ranking_url`, `observation_completeness`, public `id` (`check_...`) and available
run metadata. These list rows already contain ranking URLs; fetch
`GET /rank-checks/{check_id}` only if its detail is needed for a specific question.
Use IDs returned by this instance, not old CUID examples or run IDs.
## 3. Compare only supported observations
For a within-window movement summary, compare the earliest and latest suitable
checks in that window. Numeric delta is latest position minus earliest position;
a negative delta is an improvement. Label the actual observation dates. This is
not automatically a comparison against the previous calendar week: fetch the
prior window separately if that is what the user requested.
- A valid positive rank remains evidence even when observation coverage is truncated.
- Null position is not zero and is not automatically a loss. Only
`observation_completeness: "complete"` supports absence within the applicable
depth; unknown, missing or truncated coverage cannot establish a no-match.
- Report top-ten entries/exits only when both observations support the conclusion.
Keep unknown coverage and changes of measurement scope out of numeric deltas.
- No completed checks means missing evidence. One suitable check means no
within-window comparison. Report both cases rather than inventing movement.
- State denominator and comparable-keyword count when summarizing average change.
## 4. Add competitor context only when useful
`GET /projects/{project_id}/competitors` returns managed domains plus current
market observations and quality in `meta.markets`. Use it only when the user
requests competitor context or it explains a highlighted term. State its market,
measurement time and coverage. This current snapshot does not establish whether a
competitor gap widened or closed over the reporting week. That claim requires
separate comparable historical evidence; report the limitation if unavailable.
## 5. Deliver a concise report
Include window/time zone, scope, comparable-keyword count, main numeric gainers
and losers with old/new positions, dates and ranking URLs, supported top-ten
changes, and coverage or freshness gaps. Separate optional current competitor
context from historical changes. Give one evidence-backed next action.
Never trigger new checks to fill gaps, save a report unless separately requested,
or present a retained historical result as proof of current live rankings.
Read [references/api.md](references/api.md) for the endpoint contract.
Files in this package (2)
- SKILL.md 4 KB
- references/api.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · corgicorner/bisibility | 100 | AGPL-3.0 |
| hayat-nextoriainfotech/social-media-skills | 100 | MIT |
| logly/mureo | 100 | Apache-2.0 |
| calven-ai/marketing-as-code | 100 | MIT |
| Jackmeson1/semis-weekly | 100 | MIT |
| lingegrace/claude-research-skills | 100 | MIT |
| fabiozagaria/learning-ledger | 100 | MIT |
| zhbehx/weekly-report | 100 | MIT |
| xuanyuanli/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version f6aadb7eca9b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90seo-audit
Audit a Bisibility project's SEO using separate Search Console history, saved rank observations and a bounded website crawl, plus already-saved AI reports. Use for a requested site SEO audit or combined technical, content and visibility review. Do not use for keyword research… - 100weekly-report-writer
Generate a client-ready weekly SEO report from week-over-week GSC data. Use when the user says "write my weekly SEO report", "weekly GSC report", "client SEO update", "WoW performance summary", "what changed this week", or pastes current + prior week Search Console exports.… - 100weekly-review
Structured weekly business review and planning session. Use when user says "weekly review", "let's do a review", "what happened this week", or at the start of a new week. - 100google-ads-weekly-report
Write the weekly business review for a Google Ads account from live data, with a performance snapshot for the last complete Monday-to-Sunday week (weekly trend, WoW, YoY, month-to-date and year-to-date, plus channel and country breakdowns), root-cause investigation of the… - 100routine-weekly
Runs a short weekly review. Looks back at the week, checks follow-ups, prepares next week's calendar, and chooses next week's tasks within the free hours. Use when the user says "weekly review", "plan next week", "review my week" or runs /routine-weekly, or on the weekly review day of the profile. - 90weekly-site-and-ad-report
Use this skill on the fixed day each week when a client's site traffic and paid campaigns need reporting, and the report has to say what to do rather than what happened. Produces a short report: the five numbers that matter against last week and the four-week average, what moved…