team-performance-report

team-performance-report is a skill for Claude Code from First-Touch-Inc/firsttouch-agent-skill-packs. It costs 71 tokens per session (845 once invoked), scanned A, original, MIT.

A reporting workflow for FirstTouch outreach data over a chosen date range. It summarizes sends, replies, sentiment when available, meetings, opportunities, and whether activity was recorded in HubSpot, a customer-relationship management system.

In plain words
What is it for?
Use it for monthly or quarterly performance reviews, comparisons by flow or sender, reply and meeting analysis, and opportunity reconciliation with HubSpot.
Why use it?
It helps revenue teams see which campaigns or senders are producing engagement and whether results can be tied to pipeline. It replaces scattered activity checks with a defined report.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the bdr-pack plugin — 1 skill shipped together

Good fit Use it for monthly or quarterly performance reviews, comparisons by flow or sender, reply and meeting analysis, and opportunity reconciliation with HubSpot.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/first-touch-inc/firsttouch-agent-skill-packs/team-performance-report
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add First-Touch-Inc/firsttouch-agent-skill-packs --skill team-performance-report
Clone the repo
git clone --depth 1 https://github.com/First-Touch-Inc/firsttouch-agent-skill-packs

Made for: Claude Code.

Or install bdr-pack, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for team-performance-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/first-touch-inc/firsttouch-agent-skill-packs/team-performance-report/github.svg)](https://agentmods.dev/skills/first-touch-inc/firsttouch-agent-skill-packs/team-performance-report)
Your own site
<a href="https://agentmods.dev/skills/first-touch-inc/firsttouch-agent-skill-packs/team-performance-report"><img src="https://agentmods.dev/badge/skills/first-touch-inc/firsttouch-agent-skill-packs/team-performance-report/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for team-performance-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/first-touch-inc/firsttouch-agent-skill-packs/team-performance-report"><img src="https://agentmods.dev/badge/skills/first-touch-inc/firsttouch-agent-skill-packs/team-performance-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 845 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.00845
Opus 5 $0.00036 $0.00423
Sonnet 5 $0.00014 $0.00169
Haiku 4.5 $0.00007 $0.00085

Measured 9d ago against content hash 53f9ee8d30a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

team-performance-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/bdr-pack/skills/team-performance-report/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team Performance Report

Outcome: Give RevOps a recurring performance report, not just a setup audit: what ran, who sent it, how prospects engaged, and whether the results are attributable.

First-run onboarding gate

Run the first-run gate in ../../references/onboarding.md before first use, unless onboarding has already been completed for this workspace. Confirm reporting date range, flows/campaigns to include, and whether HubSpot is connected for opportunity/pipeline reconciliation.

When to use

  • "Show me FirstTouch performance for the last 30 days"
  • "Which flows are driving replies or meetings?"
  • "Report by sender for this month"
  • "Prove whether the rollout is working"
  • Monthly or quarterly RevOps attribution reviews

Inputs

  • Date range: default trailing 30 days
  • Scope: all team, selected flow plans, selected senders, or selected cohort/tag when available
  • Breakdown: by flow, sender, day/week/month, or source
  • HubSpot status: connected or not connected for opportunity/pipeline reconciliation

Step-by-step

1. Define report scope

Capture the requested date range, flow/campaign names, sender/team members, and whether the user wants totals, trends, or per-sender rankings. If scope is missing, default to trailing 30 days and all accessible FirstTouch team activity.

2. Pull FirstTouch team metrics

Use the FirstTouch team metrics capability for the selected date range and filters. Include, when available:

  • actions sent
  • email and LinkedIn engagement
  • replies
  • reply sentiment
  • meetings booked
  • opportunities
  • flow/source and sender breakdowns
  • chart/trend buckets only when the user asks for a trend

If metrics are unavailable or permissions are missing, mark the report unverified and state the missing access rather than inventing numbers.

3. Reconcile attribution coverage

If HubSpot is connected, compare performance reporting against HubSpot logging coverage and opportunity visibility. If HubSpot is not connected, report FirstTouch outcomes only and state that CRM opportunity/pipeline reconciliation is unavailable.

Read the full file on GitHub · 92 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 92 lines · 71 tokens per session scan A 53f9ee8d30a8

Subscribe to this mod's changes

team-performance-report is a skill published in the GitHub repository First-Touch-Inc/firsttouch-agent-skill-packs (5 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 845 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.