Source profileQuality 95/100

respira-press/agent-skills-wordpress/skills/activity-report-composer/SKILL.md

activity-report-composer

Use when the user asks for a client report, a monthly or activity report, a case study draft, or says 'what did i ship this month'. Turns the site audit log into a written report in one of six framings: agency client report, case study, internal recap, testimonial draft, build-in-public, personal recap.

Source repository stars
40
Declared platforms
0
Static risk flags
0
Last source update
2026-08-04
Source checked
2026-08-05

Decision brief

What it does—and where it fits

Version: 1.0.0 Updated: 2026-05-24 Category: reporting Status: stable Requires: Respira for WordPress plugin 7.1+ + MCP server

Best for

  • End of month — generate a client report for billing
  • Quarterly review — build-in-public summary for socials
  • Pitching a case study to a prospect

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/respira-press/agent-skills-wordpress --skill "skills/activity-report-composer"
Safe inspection promptEditorial

Inspect the Agent Skill "activity-report-composer" from https://github.com/respira-press/agent-skills-wordpress/blob/10821eaabe362fe9052f6ee81ecdd62e5d2f2980/skills/activity-report-composer/SKILL.md at commit 10821eaabe362fe9052f6ee81ecdd62e5d2f2980. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Execution Workflow

    Call respiragetactivesite. Ask the user which window to summarize: default is the last 30 days. Common windows: 7 days (weekly), 30 days (monthly), 90 days (quarterly).

    Markdown — for pasting into a doc, Notion, Linear, emailEmail-ready HTML — for sending directly through the agency's mail clientSocial-shaped — short version for LinkedIn or X (build-in-public + testimonial framings only)
  2. 02

    Step 1 — Confirm site + window

    Call respiragetactivesite. Ask the user which window to summarize: default is the last 30 days. Common windows: 7 days (weekly), 30 days (monthly), 90 days (quarterly).

    Call respiragetactivesite. Ask the user which window to summarize: default is the last 30 days. Common windows: 7 days (weekly), 30 days (monthly), 90 days (quarterly).
  3. 03

    Step 2 — Confirm framing

    Ask the user which of the six framings to use. If they don't say, recommend based on the trigger phrase ("client report" → agency client report; "build in public" → build in public framing). Default if unspecified: agency client report.

    Ask the user which of the six framings to use. If they don't say, recommend based on the trigger phrase ("client report" → agency client report; "build in public" → build in public framing). Default if unspecified: agen…
  4. 04

    Step 3 — Pull the structured data

    Call respiragenerateactivityreport with the window and framing. The tool returns:

    Call respiragenerateactivityreport with the window and framing. The tool returns:
  5. 05

    Step 4 — Compose the report in the chosen framing

    Write the report using the framing's voice:

    Write the report using the framing's voice:Agency client report — addressed to the client by name, leads with the headline number (hours saved, cost saved), then the work summary, then next steps. Professional, no informalities.Case study — third-person narrative. "Acme Inc. reduced their content production time by 40% in 30 days using Respira-augmented AI workflows." Anonymize toggle: if enabled, replace the client name with "a B2B SaaS compa…

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score95/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars40SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
respira-press/agent-skills-wordpress
Skill path
skills/activity-report-composer/SKILL.md
Commit
10821eaabe362fe9052f6ee81ecdd62e5d2f2980
License
MIT
Collected
2026-08-05
Default branch
main
View the original SKILL.md

Activity Report Composer

Version: 1.0.0 Updated: 2026-05-24 Category: reporting Status: stable Requires: Respira for WordPress plugin 7.1+ + MCP server


Description

Turn the audit log of work done on a WordPress site into a polished, written report. This skill wraps the new v7.1 respira_generate_activity_report MCP tool, which returns structured data (totals, top tools used, hours saved, cost saved at agency rate, highlights). The skill then walks the agent through writing that data into one of six framings.

The six framings:

  1. Agency client report — formal, results-focused, addressed to the client
  2. Case study — third-person narrative for marketing, anonymize-toggle available
  3. Internal recap — for team standups, terse, what shipped + what's next
  4. Testimonial draft — first-person, optimized as a customer quote
  5. Build in public — public-facing, social-media-shaped, what got done this week
  6. Personal recap — for the operator's own records, no marketing varnish

When to Use

  • End of month — generate a client report for billing
  • Quarterly review — build-in-public summary for socials
  • Pitching a case study to a prospect
  • Capturing testimonial language while the work is fresh
  • Internal weekly review for an agency team

Trigger Phrases

  • "generate a client report"
  • "make a monthly report"
  • "activity report"
  • "compose an activity report"
  • "build an agency client report"
  • "draft a case study from this site"
  • "build-in-public summary"
  • "internal recap"
  • "what did i ship this month"
  • "client billing report"

Execution Workflow

Step 1 — Confirm site + window

Call respira_get_active_site. Ask the user which window to summarize: default is the last 30 days. Common windows: 7 days (weekly), 30 days (monthly), 90 days (quarterly).

Step 2 — Confirm framing

Ask the user which of the six framings to use. If they don't say, recommend based on the trigger phrase ("client report" → agency client report; "build in public" → build in public framing). Default if unspecified: agency client report.

Step 3 — Pull the structured data

Call respira_generate_activity_report with the window and framing. The tool returns:

{
  "client": "string",
  "window": "30 days",
  "framing": "agency_client_report",
  "hoursSaved": "5.1",
  "costSaved": {"amount": "408", "currency": "EUR"},
  "totals": {"edits": 42, "pages": 14, "snapshots": 27, "rollbacks": 2},
  "topTools": [
    {"name": "respira_update_module", "scope": "write", "n": 14},
    {"name": "respira_extract_builder_content", "scope": "read", "n": 23}
  ],
  "notes": ["Migrated 14 blog posts to /journal/...", "..."]
}

Step 4 — Compose the report in the chosen framing

Write the report using the framing's voice:

Agency client report — addressed to the client by name, leads with the headline number (hours saved, cost saved), then the work summary, then next steps. Professional, no informalities.

Case study — third-person narrative. "Acme Inc. reduced their content production time by 40% in 30 days using Respira-augmented AI workflows." Anonymize toggle: if enabled, replace the client name with "a B2B SaaS company" or similar. Anonymize all identifying details in the highlights.

Internal recap — bullets, no narrative. "42 edits, 14 pages touched, 0 rollbacks. Top time-saver: bulk Divi module updates. Next: ship the pricing page redesign."

Testimonial draft — first-person, in the operator's voice, framed as a quote. "In the last 30 days I saved 5 hours of agency time on [client] thanks to Respira's snapshot-first edits. We shipped 14 pages with zero rollbacks."

Build in public — punchy, social-shaped. "This week on Respira: 42 edits across 14 client pages, 5 hours saved, 0 rollbacks. The agent took a swing, snapshotted before every change, and not once did I have to undo it. Here's what landed →"

Personal recap — terse log entry for the operator's own notes. Date, totals, what got done, what was hard, what's next. No marketing voice.

Step 5 — Offer three output formats

After the report is composed, ask the user which output they want:

  • Markdown — for pasting into a doc, Notion, Linear, email
  • Email-ready HTML — for sending directly through the agency's mail client
  • Social-shaped — short version for LinkedIn or X (build-in-public + testimonial framings only)

Step 6 — Save (optional)

Offer to save the report as a custom post type entry on the site (so it shows up in the Activity reports archive). Use respira_create_custom_post with post_type=respira_activity_report if that CPT exists.


Output template — Agency client report (example)

# Activity Report: {client_name} — {window}

**{hoursSaved}h of work saved · €{costSaved} at our standard rate**

## Summary

In the last {window}, {totals.edits} edits landed across {totals.pages} pages on {client_name}'s site. {totals.snapshots} snapshots were captured before any change, and {totals.rollbacks} were rolled back during review.

## What we did

{notes formatted as bullet list}

## Top operations

{topTools formatted as a small table — name, read/write, count}

## Next steps

{agent fills in — could be empty if no obvious next steps, or could reference open work}

---

Prepared by Respira for {client_name} · {date}

Anonymization rules (case-study framing only)

If the user selects case-study framing with anonymize ON:

  • Replace client name everywhere with industry descriptor ("a B2B SaaS company", "a Lisbon-based design agency", "a multi-location restaurant group")
  • Replace specific URLs with [client website]
  • Replace named pages with generic descriptors ("the pricing page", "the careers section", "a long-form sales landing page")
  • Replace named team members with role descriptors ("their head of marketing", "the founder")
  • Keep all numbers exact — they are the proof
  • Note "Customer data anonymized at customer's request" at the bottom

Hard rules

  • Never invent numbers. Every figure in the report comes from the respira_generate_activity_report response or from the totals counted in the audit log. If the data is empty, say so — do not pad.
  • Never name customers in the build-in-public or social outputs unless the user explicitly OKs it for this specific report. Default to "a client" or "an agency I work with."
  • The hours-saved + cost-saved numbers in the structured data already factor in the operator's stated rate. Do not multiply or convert them.
  • Reports are an output, not a record. They live in the user's Markdown / email / dashboard, not in the audit log itself.

Telemetry

Records: site URL hash, framing chosen, window length, totals from the response, output format selected, success/failure. No report text, no client name, no notes are sent.

Endpoint: POST https://www.respira.press/api/skills/track-usage

Alternatives

Compare before choosing

Computed 9313,363

AgriciDaniel/claude-seo

seo-ecommerce

E-commerce SEO analysis: Google Shopping visibility, Amazon marketplace intelligence, product schema validation, competitor pricing analysis, and marketplace keyword gaps. Combines on-page product SEO with marketplace data from DataForSEO Merchant API. Use when user says "ecommerce SEO", "product SEO", "Google Shopping", "marketplace SEO", "product schema", "Amazon SEO", "product listings", "shopping ads", or "merchant SEO".

Computed 9340

respira-press/agent-skills-wordpress

seo-aeo-amplifier

Use when the user says 'run an seo aeo audit', 'improve my search visibility', 'optimize my site for search engines', or wants the site cited by AI answer engines. Audits on-page SEO and AEO, generates schema markup, and applies fixes on duplicates for review after a snapshot.

Computed 923,318

nowork-studio/NotFair

seo-analysis

Full SEO audit: Google Search Console data + URL Inspection API + PageSpeed Insights API + technical crawl + keyword research + metadata audit + schema markup audit + search intent analysis + Core Web Vitals monitoring. Feeds real GSC data and PageSpeed metrics into AI to surface quick wins, diagnose traffic drops, find content gaps, identify metadata mismatches, detect schema gaps, monitor page performance, and produce an actionable 30-day plan. Use this skill whenever the user asks about SEO,

Computed 922,509

aaron-he-zhu/aaron-marketing-skills

performance-monitor

Use it for seo audit and marketing tasks; the detail page covers purpose, installation, and practical steps.