content-generate-rec-issuer-quirks

Correct issuer-specific REC content with YAML-driven HTML fixes and image sourcing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the inconsistency problem where issuer-specific credit-card pages require special handling, post-processing, and fallback image sourcing to produce publishable, accurate content.

Core Features & Use Cases

  • Issuer URL & extraction quirks: Handles American Express UK, Barclaycard, Capital One UK, NatWest, and Lloyds Bank differences in URL patterns and page behavior.
  • Correct card image sourcing: Uses deterministic CDN patterns where available and a Bing Images + Playwright local fallback for geo-blocked domains.
  • Content repair & normalization: Fixes malformed API HTML closing tags, collapses duplicate headings, injects required table styling, and enforces subtitle length constraints with cascade-safe resizing.

Quick Start

Use this skill alongside content-generate-rec to generate and validate issuer-specific REC content (including images and HTML fixes) for American Express UK, Barclaycard, Capital One UK, NatWest, or Lloyds Bank.

Frequently Asked Questions about content-generate-rec-issuer-quirks

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

FAQPage Schema
How do I fix credit card content extraction failures for UK issuer pages with non-uniform URLs?▼

Credit card content extraction failures for UK issuers are fixed by applying YAML-driven companion reference data that handles non-uniform URLs, geo-blocked domains, and specific HTML post-processing replacements for American Express UK, Barclaycard, Capital One UK, NatWest, and Lloyds Bank pipelines.

What is the best way to source card images when an issuer's domain is geo-blocked?▼

Sourcing card images from geo-blocked issuer domains is handled by using deterministic CDN patterns where available, with a fallback to scraping Bing Images locally via Playwright to retrieve the required assets.

How do I enforce subtitle length constraints during HTML post-processing for WordPress uploads?▼

Subtitle length constraints during HTML post-processing are enforced through subtitle validation with cascade-safe resizing, ensuring all subtitles are truncated to a maximum of 100 characters before the WordPress upload occurs.

Does this content generation approach handle malformed API HTML closing tags and duplicate headings?▼

Yes, the content repair and normalization process fixes malformed API HTML closing tags, collapses duplicate headings, and injects required table styling to ensure the final HTML output is publishable.

Can I use Playwright for local web scraping to bypass geo-blocked issuer domains?▼

Playwright is used for local Bing Images scraping as a fallback mechanism to bypass geo-blocked issuer domains and retrieve card images when deterministic CDN patterns are unavailable.

When do I need issuer-specific quirks handling for REC content generation pipelines?▼

Issuer-specific quirks handling is needed when standard REC content generation produces inaccurate tables, headings, or missing card images for UK credit card publication pipelines requiring specialized extraction and HTML correction.