darling-martech-services

Govern Darling MarTech service pages under /services/[slug] with batch-driven builds.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/DarlingMarketingandTech/darling-martech --skill darling-martech-services
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: darling-martech-services
Source: https://github.com/DarlingMarketingandTech/darling-martech/tree/main/skills/darling-martech-services
Command: npx skills add https://github.com/DarlingMarketingandTech/darling-martech --skill darling-martech-services

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines and enforces a scalable governance model for Darling MarTech's service pages, including build order, content rules, and proof assignment, so teams can consistently publish and update /services/[slug] pages.

Core Features & Use Cases

  • Structure & routing guidance for all child-service pages under /services/[slug].
  • Proof matrix integration to assign a dominant primary proof plus supporting proofs with clear rationales.
  • Batch-driven workflow providing a repeatable sequence for launching and rewriting service pages, plus guidelines for content and SEO.
  • Route metadata conventions to ensure each new route ships with its own metadata export.

Quick Start

Create a new child-service page under /services/[slug] using the documented templates and routing rules.

Frequently Asked Questions about darling-martech-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce slug conventions and metadata for service pages?

Service page routing governance works by enforcing specific slug conventions under the /services/[slug] directory, ensuring each new route ships with its own metadata export and required frontmatter to maintain a scalable structure.

What is a proof matrix and how does it assign proofs to service pages?

A proof matrix assigns a dominant primary proof along with supporting proofs to service pages, providing clear rationales for each assignment to ensure content validity and structural consistency across the site.

How to build service pages using a batch-driven workflow?

Build service pages using a batch-driven workflow by following a repeatable sequence for launching and rewriting pages, which integrates documented templates, routing rules, and content guidelines to standardize the process.

Do I need metadata exports for every new service page route?

Yes, route metadata conventions require that each new route ships with its own dedicated metadata export to maintain governance and ensure the service page system scales correctly without structural errors.

What are the limitations of manual service page governance without batch workflows?

Without batch-driven workflows, service page governance becomes inconsistent, leading to broken slug conventions, missing required frontmatter, and unstructured proof assignments that fail to scale across multiple pages.