30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
4.4 KiB
4.4 KiB
G2
Software review and research platform for B2B buyers. Access reviews, product data, competitor comparisons, and buyer intent signals.
Capabilities
| Integration | Available | Notes |
|---|---|---|
| API | ✓ | Reviews, Products, Reports, Categories, Tracking |
| MCP | - | Not available |
| CLI | ✓ | g2.js |
| SDK | - | REST API with JSON:API format |
Authentication
- Type: API Token
- Header:
Authorization: Token token={YOUR_API_TOKEN} - Content-Type:
application/vnd.api+json(JSON:API) - Get token: G2 Admin Portal > Integrations > API Tokens
- Docs: https://data.g2.com/api/docs
Common Agent Operations
List reviews (survey responses)
GET https://data.g2.com/api/v1/survey-responses?page[size]=25&page[number]=1
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
Get a specific review
GET https://data.g2.com/api/v1/survey-responses/{id}
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
Filter reviews by product
GET https://data.g2.com/api/v1/survey-responses?filter[product_id]={product_id}&page[size]=25
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
List products
GET https://data.g2.com/api/v1/products?page[size]=25&page[number]=1
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
Get a specific product
GET https://data.g2.com/api/v1/products/{id}
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
List reports
GET https://data.g2.com/api/v1/reports?page[size]=25&page[number]=1
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
List categories
GET https://data.g2.com/api/v1/categories?page[size]=25&page[number]=1
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
Get competitor comparisons
GET https://data.g2.com/api/v1/competitor-comparisons?filter[product_id]={product_id}&page[size]=25
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
Get tracking events (buyer intent)
GET https://data.g2.com/api/v1/tracking-events?filter[start_date]=2025-01-01&filter[end_date]=2025-12-31
Headers:
Authorization: Token token={API_TOKEN}
Content-Type: application/vnd.api+json
API Pattern
G2 follows the JSON:API specification (https://jsonapi.org/):
- Responses use
data,attributes,relationships,metastructure - Pagination:
page[number]andpage[size]query parameters - Filtering:
filter[field]=valuequery parameters - Reviews returned newest-first by default (10 per page default)
Key Metrics
Review Metrics
star_rating- Overall star ratingtitle- Review titlecomment_answers- Structured review responses (likes, dislikes, recommendations)submitted_at- Review submission dateis_public- Whether the review is publicly visible
Product Metrics
name- Product nameslug- URL slug on G2avg_rating- Average star ratingtotal_reviews- Total review countcategory- G2 category placement
Buyer Intent (Tracking)
company_name- Visiting company namepage_visited- G2 page URL visitedvisited_at- Visit timestampactivity_type- Type of buyer activity
Parameters
Pagination
page[number]- Page number (default: 1)page[size]- Items per page (default: 10, max: 100)
Review Filters
filter[product_id]- Filter by product IDfilter[state]- Filter by review state
Tracking Filters
filter[start_date]- Start date (YYYY-MM-DD)filter[end_date]- End date (YYYY-MM-DD)
When to Use
- Monitoring and analyzing software product reviews
- Tracking buyer intent signals from G2 visitors
- Pulling competitor comparison data for positioning
- Feeding review data into CRM or marketing automation
- Building social proof content from G2 reviews
- Tracking G2 category rankings and report placements
Rate Limits
- 10,000 requests per hour per API token
- Implement exponential backoff on 429 responses
- Cache results where possible to reduce API calls
Relevant Skills
- competitors
- social-proof
- reputation-management
- customer-feedback
- review-generation