Skip to content

Reusable Modules

One of the key Year 1 success metrics is reuse rate — new agents should leverage shared modules rather than rebuilding common functionality. This guide documents the reusable components available and how to use them.

Why Reusable Modules Matter

From the Year 1 Success Criteria:

"Net-new agents that don't reuse shared skills increase maintenance load and audit surface area. Reuse rate becomes a Year 1 scaling gate."

Benefits of reuse:

  1. Consistency — Same standards applied everywhere
  2. Maintenance — Fix once, fix everywhere
  3. Quality — Battle-tested components
  4. Speed — Don't reinvent the wheel
  5. Trust — Proven patterns reduce risk

The rule: New agents should use ≥3 shared modules to qualify for approval.

Module Types

Reusable modules can be implemented as different component types depending on their purpose:

Module Type When to Use Implementation
Skill Automatic behavior based on context skills/{skill-name}/SKILL.md
Hook Event-driven automation hooks/hooks.json
Command User-triggered workflow commands/{command}.md
Template Output structure/format Resource file in skill
Script Programmatic validation scripts/{script}.py

Available Shared Modules

Core Skills (from core-dependencies)

Module Type Purpose When It Activates
writing-standards Skill Seer voice and tone Deliverables, client content
quality-standards Skill Data quality, citations, trust guardrails Analysis, projections, recommendations
prompt-engineering Skill Prompt optimization patterns Complex prompts, multi-step reasoning

Output Components

These are standardized output patterns documented in skills that all agents should use:

Executive Summary Module

Purpose: Consistent high-level summary format

Structure: 

## Executive Summary

**Key Findings:**

- [Finding 1 with data point]
- [Finding 2 with data point]
- [Finding 3 with data point]

**Immediate Opportunities:**

- [Opportunity 1] — [Expected impact]
- [Opportunity 2] — [Expected impact]

**Recommended Next Steps:**
1. [Action 1] — [Timeline]
2. [Action 2] — [Timeline]
3. [Action 3] — [Timeline]

Source: writing-standards skill

Findings Rubric Module

Purpose: Consistent severity classification

Structure: | Severity | Definition | Visual | |----------|------------|--------| | Critical | Blocking issue, immediate action required | 🔴 | | High | Significant impact, prioritize within sprint | 🟠 | | Medium | Notable opportunity, schedule for roadmap | 🟡 | | Low | Nice-to-have, address when capacity allows | 🟢 |

Usage: 

### Finding: Missing FAQ Section
**Severity:** High 🟠
**Rationale:** 8 PAA questions identified; top 3 competitors all have FAQ sections
**Recommendation:** Add FAQ targeting top 5 PAA questions
**Effort:** Low (2-3 hours)

Source: quality-standards skill

Effort/Impact Table Module

Purpose: Consistent prioritization format

Structure: | Recommendation | Effort | Impact | Priority | SOW Coverage | |----------------|--------|--------|----------|--------------| | [Rec 1] | Low | High | 1 | ✅ In scope | | [Rec 2] | Medium | High | 2 | ⚠️ Upsell | | [Rec 3] | High | Medium | 3 | ✅ In scope |

Effort Levels:

  • Low: <4 hours, no dev required
  • Medium: 4-16 hours, may need dev support
  • High: >16 hours, significant resources

Impact Levels:

  • Low: Incremental improvement
  • Medium: Measurable business impact
  • High: Strategic importance

Source: seo-methods skill (SEO division)

Team Lead Review Checklist Module

Purpose: Pre-delivery QA gate

Structure: 

## Team Lead Review Checklist

Before approval, verify:

### Data Quality
- All data sources cited with date ranges
- Math verified (percentages, growth rates)
- Sample sizes sufficient for conclusions

### Recommendations
- Each recommendation has rationale + evidence
- No ungrounded numeric claims
- Effort/impact assessments realistic

### Client Readiness
- No internal Seer data exposed
- Language appropriate for client audience
- Formatting clean and professional

### Approval
- Reviewed by: _______________
- Date: _______________
- Status: Approved / Needs Revision

Source: quality-standards skill

Upsell Opportunities Module

Purpose: Identify revenue expansion opportunities

Structure: 

## Upsell Opportunities

Based on findings, these services could provide additional value:

| Opportunity | Rationale | Est. Investment | Alignment |
|-------------|-----------|-----------------|-----------|
| [Service 1] | [Why needed based on findings] | $X,XXX | [Client goal] |
| [Service 2] | [Why needed based on findings] | $X,XXX | [Client goal] |

**Note:** Pricing based on standard rate card. Custom scoping available.

Source: Division-specific skills

Trust Guardrails (Hooks)

Module Type Purpose Trigger
No-Ungrounded-Claims Quality check Flags numeric assertions without source PostToolUse
Source-Attribution Quality check Ensures data citations present Stop hook

Implementation: These are enforced via the quality-standards skill and can be checked programmatically.

How to Use Shared Modules

In Agent Definitions

Reference skills in agent frontmatter:

---
name: my-new-agent
description: "Does something useful"
metadata:
  skills: [writing-standards, quality-standards, seo-methods]
  quality-tier: peer-review
---

In Output Templates

Reference module patterns in your agent's output section:

## Output Format

This agent produces a structured report using:
- Executive Summary (per writing-standards)
- Findings with severity classification (per quality-standards)
- Prioritized recommendations with Effort/Impact table
- Team Lead Review Checklist

See [Reusable Modules](link) for format specifications.

In Workflow Steps

Call out module usage in methodology:

## Process & Methodology

### Step 3: Synthesize Findings
Apply findings rubric (Critical/High/Medium/Low) to each issue.
Reference: quality-standards severity classification.

### Step 4: Generate Recommendations
Create Effort/Impact table for all recommendations.
Reference: seo-methods prioritization format.

### Step 5: Pre-Delivery QA
Complete Team Lead Review Checklist before export.
Reference: quality-standards pre-delivery checklist.

Creating New Shared Modules

When to Create a New Module

Create a shared module when:

  1. Pattern repeats — Same structure used in 3+ agents
  2. Consistency matters — Variations cause confusion
  3. Quality is critical — Standardization reduces errors
  4. Maintenance burden — Fixing in one place is better

Module Creation Process

  1. Identify the pattern — Document current usage across agents
  2. Standardize the format — Create canonical structure
  3. Choose implementation type — Skill, hook, command, template, or script
  4. Add to core-dependencies — If cross-division; otherwise, division skill
  5. Document in this guide — Add to "Available Shared Modules" section
  6. Update existing agents — Migrate to use the new module

Module Documentation Template

#### [Module Name] Module

**Purpose:** [One-line description]

**Structure:**
[Show the canonical format/template]

**Usage:**
[Example of how to use in an agent]

**Source:** [Which skill/hook provides this]

**Notes:** [Any caveats or variations]

Module Reuse Checklist

Before submitting a new agent for review, verify:

  • Uses writing-standards skill for any client-facing content
  • Uses quality-standards skill for any data analysis
  • Uses Executive Summary format for high-level findings
  • Uses Findings Rubric (severity levels) for issues
  • Uses Effort/Impact table for recommendations
  • Includes Team Lead Review Checklist
  • Total: ≥3 shared modules used

Agents with <3 shared modules will be sent back for redesign.

Module Inventory by Division

SEO Division (seo-methods skill)

Additional modules beyond core:

  • Content scoring rubric
  • Keyword opportunity template
  • SERP feature analysis format
  • Competitor comparison table

PDM Division (planned)

  • Campaign performance summary
  • Creative analysis template
  • Budget allocation table
  • Keyword efficiency matrix

Client Services Division (planned)

  • QBR outline structure
  • Period comparison format
  • Strategic roadmap template
  • Action item tracker

Last updated: 2026-01-26