content-generate-rec

Route deterministic REC, P1, and REC+P1 credit-card content generation and publication.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mattei2005/mgs-agent --skill content-generate-rec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-generate-rec
Source: https://github.com/mattei2005/mgs-agent/tree/main/skills/content-generate-rec
Command: npx skills add https://github.com/mattei2005/mgs-agent --skill content-generate-rec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sqlite3, curl, jq, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill routes deterministic generation, validation, and safe publication of credit-card REC, P1, and combined REC+P1 content without relying on editorial card cache.

Core Features & Use Cases

  • Deterministic runner routing: Use the approved REC runner for REC jobs and the orchestrator for REC+P1, ensuring consistent execution order and hard gating.
  • No editorial cache policy: Prevents using cached editorial facts for benefits, APR, fees, eligibility, descriptors, copy, official URLs, or card imagery.
  • Image identity & quality gates: Enforces card-only LazyBlock images, horizontal normalization rules, and featured-image separation so REC and P1 do not reuse the same featured media.
  • Validation-first reporting: Blocks or reports failures when public verification, image validation, Yoast/readability, or required links fail, and requires evidence for cleanup after failed runs.

Quick Start

Use the content-generate-rec skill when you need Atena to create or publish REC, P1, or REC+P1 credit-card content from verified official facts, following the deterministic runner/orchestrator commands.

Frequently Asked Questions about content-generate-rec

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

FAQPage Schema
How do I generate credit card content without relying on editorial cache?

Generate credit card content without editorial cache by routing deterministic REC, P1, and REC+P1 jobs through approved local runners and validators. This enforces a strict no-editorial-cache policy, blocking cached facts for benefits, APRs, fees, and card imagery.

What is a no-editorial-cache policy for credit card content generation?

A no-editorial-cache policy prevents the use of cached editorial facts for benefits, APR, fees, eligibility, descriptors, copy, official URLs, and card imagery. It ensures content generation uses only official-source facts or explicitly verified request facts.

How do I validate horizontal card-only images for REC and P1 content?

Validate horizontal card-only images by applying image identity and quality gates. This enforces card-only LazyBlock imagery, horizontal normalization rules, and featured-image separation so REC and P1 do not reuse the same featured media.

Can I use python3 and jq for REC+P1 content orchestration?

Yes, REC+P1 content orchestration supports python3 and jq. The orchestrator uses these dependencies to route deterministic generation and publication, ensuring consistent execution order and hard gating for combined operations.

Why does credit card content publication fail during Yoast and readability validation?

Credit card content publication fails during Yoast and readability validation when public verification, image validation, or required links fail. The validation-first reporting blocks publication and requires evidence for orphan-media cleanup after failed runs.

When do I need distinct featured images for REC+P1 credit card operations?

You need distinct featured images for REC+P1 credit card operations to enforce image identity and quality gates. This separation ensures REC and P1 content do not reuse the same featured media, maintaining visual distinction between content types.