mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-11 19:47:12 +03:00

Files

T

6f67a34ef1 feat(skill): cross-pollinate the new tool wave into catalog routing (#275 )

* feat(skill): cross-pollinate the new tool wave into catalog routing

Wire the recent tool skill wave into the two-layer routing graph so the
new tool skills are reachable from the methodology skills that own their
domains, and vice versa:

- methodology -> tool down-routes: platform-engineering -> kubernetes,
  terraform, telemetry, postgres, grafana; site-reliability-engineering ->
  telemetry, grafana; data-engineering and backend-engineering -> postgres;
  frontend-engineering -> mobile-development; verification-methodology ->
  playwright, documents; technical-documentation -> documents
- neckbeard: add mobile-development and documents routing rows plus
  change-surface coverage entries, and cross-link the lightweight
  test-hardening path to qa-methodology's bounded mutation-review material
- collaboration layer: chief-of-staff-methodology -> slack/notion/email,
  go-to-market -> crm, conditional-customer-success -> crm; fix the dead
  seo-content-optimization reference in go-to-market (now seo-audit)
- references/skill-triggers.md: add trigger rows for the 14 new skills
- bring go-to-market's description up to the quality validator's
  imperative-verb + negative-boundary requirement and regenerate catalogs

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

* fix(skill): add eval manifest for technical-documentation

The eval-coverage ratchet fails on modified skills without a schema-valid
manifest once coverage passes 50%. technical-documentation was modified by
the routing cross-pollination change and lacked one; add six output-quality
cases covering README authorship, API reference generation, CLI help design,
agent-facing docs, documentation-site IA, and troubleshooting sections.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

---------

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

2026-08-04 12:46:06 -04:00

3.9 KiB

Raw Blame History

name, description, license, metadata

name

description

license

metadata

go-to-market

Plan and execute go-to-market strategy — positioning and messaging frameworks (April Dunford's positioning, message hierarchy), customer acquisition strategy (paid, organic, PLG, SLG), brand architecture (brand house vs house of brands), growth modeling (CAC/LTV by channel, cohort analysis), market entry strategy (beachhead, land-and-expand), and competitive response (pricing wars, feature races, brand defense). Do not use for sales execution and pipeline management, product strategy, or visual brand identity design.

MIT

tags	source_repo
go-to-market, cmo, marketing, positioning, messaging, acquisition, brand-architecture, growth-modeling, competitive-response, plg, slg	https://github.com/magnus919/hermes-profiles

Go-to-Market — CMO Methodology

CMO-level methodology for go-to-market strategy, positioning, acquisition, brand, and growth modeling. This skill provides the frameworks and reference material for a chief marketing officer profile.

When to Load

Trigger	What's Needed
Define positioning and messaging	`references/positioning-messaging.md` — Dunford framework, message hierarchy
Build acquisition channel strategy	`references/acquisition-strategy.md` — channel mix, PLG/SLG, funnel metrics
Design brand architecture	`references/acquisition-strategy.md` — brand systems, visual identity, brand health
Model growth economics	`references/growth-modeling.md` — CAC/LTV, cohort analysis, market entry
Develop competitive response	`references/acquisition-strategy.md` — pricing wars, feature races, brand defense
Plan market entry	`references/growth-modeling.md` — beachhead, land-and-expand, channel economics

Loading Order

skill_view('go-to-market')
# Then domain-specific references:
skill_view('go-to-market', file_path='references/positioning-messaging.md')
skill_view('go-to-market', file_path='references/acquisition-strategy.md')
skill_view('go-to-market', file_path='references/growth-modeling.md')

Reference Files

Reference	Purpose
`references/positioning-messaging.md`	April Dunford positioning, message hierarchy (elevator pitch → value prop → narrative), positioning diagnostic
`references/acquisition-strategy.md`	Channel taxonomy, PLG vs SLG playbooks, sales funnel ratios, competitive response playbook, brand architecture
`references/growth-modeling.md`	CAC/LTV deep dive, cohort analysis practical guide, NRR, market entry strategy (beachhead, land-and-expand)

Output Contract

The profile using this skill produces artifact pyramids. The response to any caller is the absolute path to 00-index.md. See artifact-pyramids skill for the specification.

When not to use

Sales execution and pipeline management — this skill owns acquisition strategy, not running the funnel. CRM operations (contact lookup, deal pipeline views, confirmed stage changes) belong to crm.
Product strategy and roadmap — product vision, PMF, and prioritization belong to product-strategy and product-methodology.
Visual brand identity design — logo, palette, and brand systems belong to brand-designer.
Marketing campaign execution — this skill defines the channel strategy and positioning; operating the channel tools is the corresponding tool skill's job.

artifact-pyramids — output contract
product-strategy — CPO methodology (product vision, PMF, market sizing)
brand-designer — visual brand identity design
seo-audit — organic search audit and content strategy
crm — HubSpot CRM operations: contact lookup, deal pipeline views, and confirmed deal stage changes

3.9 KiB Raw Blame History