[agents] Add custom GitHub Copilot agent for blog post creation

[Copilot]

Description

This PR fixes #4914

Implements a custom GitHub Copilot agent (blog-writer) that automates Layer5 blog post creation with complete adherence to site conventions and SEO best practices.

Implementation

Created .github/agents/ directory with:

• blog-writer.yml (485 lines) - Agent configuration including:

  • Core configuration: Always uses the most powerful AI model available
  • Target audience specification: Content tailored for platform engineers, DevOps engineers, SREs, IT administrators, Kubernetes operators, cloud native developers, open source contributors, solution architects, enterprise architects, and developers
  • Default author byline: "Layer5 Team" set as default for all blog posts
  • Complete frontmatter template with all required fields
  • 22 categories and 18 tags weighted by usage frequency
  • Component integration guides (BlockQuote, BlockQuoteAlt, CTA_FullWidth, CTA_Bottom, CTA_ImageOnly)
  • Blog.style.js CSS class reference
  • SEO optimization rules (title, description, URL structure)
  • Cross-linking strategy with common destinations
  • RSS feed distribution logic
  • Image sourcing guidelines (local storage, community assets)
  • Resources collection inclusion criteria
  • Audience-focused content guidelines addressing real-world challenges

• README.md (165 lines) - Agent directory overview, usage patterns, troubleshooting, with AI model and audience configuration details

• USAGE_EXAMPLES.md (342 lines) - 6 detailed scenarios (feature announcements, tutorials, community spotlights, technical deep dives, event recaps, how-tos) with audience context

• QUICK_REFERENCE.md (175 lines) - Single-page lookup table for tags, categories, components, CSS classes, with agent configuration section and default author specification

Updated AGENTS.md with custom agent section including AI model configuration and complete target audience definition.

Usage

@blog-writer Create a blog post about Meshery design patterns

Agent automatically handles:

• Uses most powerful AI model available
• Creates content tailored for technical practitioners (platform engineers, DevOps, SREs, architects)
• Sets "Layer5 Team" as default author byline
• Proper frontmatter structure
• Tag/category selection (prefers existing)
• Required graphics and CTAs
• BlockQuote placement for emphasis
• Cross-page hyperlinks to existing content
• SEO optimization
• Resources collection consideration
• Addresses real-world challenges faced by platform teams

Notes for Reviewers

All 9 requirements from issue satisfied:

1. Image sourcing guidance (local/community assets)
2. Blog template adherence
3. Weighted tag/category selection
4. Resources collection consideration
5. CSS stylesheet integration
6. Mandatory graphics/CTAs
7. BlockQuote component usage
8. Extensive cross-linking
9. SEO optimization (URL, title, headings, keywords)

Additional enhancements:

• Configured to always use most powerful AI model available
• Comprehensive target audience definition for technical practitioners
• Audience-focused content guidelines for platform engineering and operations content
• Default author byline set to "Layer5 Team" with explicit guidance

YAML syntax validated. No security issues (CodeQL).

Signed commits

• Yes, I signed my commits.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Create a custom coding agent for GitHub Copilot specific to creating blog posts</issue_title>
<issue_description>### Considerations

1. Include image generation or image sourcing from the community shared drive.
2. Include use of the blog template.
3. Ensure that existing tags and existing categories are given a heavier weight when identifying appropriate tags and categories.
4. Blogs should generally be considered for inclusion in the /resources collection, too.
5. Review the specific CSS stylesheet for blogs and consider use.
6. Always attempt to have at least one graphic and one CTA included per blog post.
7. Use BlockQuote and BlockQuoteAlt to emphasize a central point as appropriate.
8. Include as many cross-page (intra-site) hyperlinks as possible, when a topic touches on existing content or existing pages that the site has.
9. Optimize the post's published location (URL), title, headings and keywords for SEO impact.
   </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Create a custom coding agent for GitHub Copilot specific to creating blog posts #7138

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[leecalcote]

@copilot,

1. always select the most powerful AI model available.
2. understand that the primary audience for layer5.io/blog posts are platform engineers, DevOps engineers, site reliability engineers (SREs), IT administrators, Kubernetes operators, cloud native developers, open source contributors, solution architects, enterprise architects, developers and so on.

[Copilot]

@copilot,

1. always select the most powerful AI model available.
   ...

Updated the blog-writer agent to address both requirements:

1. Most Powerful AI Model: Added explicit configuration in the agent instructions to always use the most powerful AI model available for content generation.

2. Target Audience: Clarified throughout all documentation that content is specifically tailored for:

   • Platform Engineers
   • DevOps Engineers
   • Site Reliability Engineers (SREs)
   • IT Administrators
   • Kubernetes Operators
   • Cloud Native Developers
   • Open Source Contributors
   • Solution Architects
   • Enterprise Architects
   • Software Developers

The agent now includes audience-focused content guidelines that address real-world challenges faced by platform teams and operators, balancing technical depth with accessibility across experience levels.

Changes committed in f5da9d0.

[leecalcote]

@copilot, use "Layer5 Team" as the default byline.

[Copilot]

@copilot, use "Layer5 Team" as the default byline.

Set "Layer5 Team" as the default author byline throughout the agent configuration:

1. Updated frontmatter template to use author: Layer5 Team
2. Added explicit guidance: "Default: Use 'Layer5 Team' as the author byline for all blog posts"
3. Clarified to only use a specific person's name if explicitly provided or for special cases like interviews
4. Updated QUICK_REFERENCE.md with the default author

Changes committed in a74f3f0.