Skill make blog post

[jhauga]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

Skill to assist in the automation, or help in making blog post for a workspace, repo, or as a standalone post.

Porting instructions from PR 3584 to skill.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🔒 PR Risk Scan Results

Scanned 6 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🔍 Vally Lint Results

✅ All checks passed

Scope	Checked
Skills	1
Agents	0
Total	1

Severity	Count
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
ℹ️	✅ make-blog-post (2/2 checks passed)
ℹ️	✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️	✓ spec-compliance: All spec checks passed.
ℹ️	✓ [valid-refs] All file references across 1 skill(s) are valid.
ℹ️	✓ valid-refs: All file references resolve to existing files within the skill directory.
ℹ️	1 skill(s) linted, 1 passed

Full linter output

### Linting skills/make-blog-post
✅ make-blog-post (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

[Copilot]

Copilot review overview

🟡 Changes recommended

External samples need prompt-injection safeguards, and the Jekyll and voice-reuse guidance contains conflicting or inaccurate instructions.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1 · 2

Open (3)

• Treat fetched sample content as untrusted data · New
• Support configured Jekyll post extensions · New
• Resolve conflicting rules on reusing sample text · New

What changed in this PR

Adds a reusable skill for drafting code-focused blog posts with approval gates, author-voice matching, and destination-aware formatting.

Changes:

• Adds the blog-post drafting workflow and voice-profile template.
• Documents platform, delivery, SEO, and voice-matching guidance.
• Registers the skill in the generated catalog.

File	Description
skills/​make-blog-post/​SKILL.md	Defines the skill workflow and safeguards.
skills/​make-blog-post/​references/​voice-profile.md	Guides author-voice analysis.
skills/​make-blog-post/​references/​seo.md	Defines destination-specific SEO rules.
skills/​make-blog-post/​references/​delivery.md	Defines delivery formats and boundaries.
skills/​make-blog-post/​references/​blog-platforms.md	Documents generator-specific conventions.
skills/​make-blog-post/​assets/​voice-profile-template.md	Provides a reusable voice profile.
docs/​README.skills.md	Adds the skill to the catalog.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟡 Changes recommended

Invalid YAML and unresolved metadata and privacy conflicts could prevent correct or safe skill operation.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1

Open (1)

• Fix apostrophes breaking single-quoted YAML scalars · New

Resolved since last review (3)

• Treat fetched sample content as untrusted data
• Resolve conflicting rules on reusing sample text
• Support configured Jekyll post extensions

Previously missed (2)

In code that hasn't changed since last review

Prevent persistence of private URLs and local paths

skills/​make-blog-post/​assets/​voice-profile-template.md:10

The skill recommends saving this profile in the blog repository, but these placeholders allow private URLs and absolute local paths to be persisted there. That can expose usernames, machine paths, or private source locations when the repository is published; constrain saved references to public URLs or safe repository-relative paths.

Require author identity confirmation before voice filtering

skills/​make-blog-post/​references/​voice-profile.md:19

On a multi-author site, filtering by an author field still requires knowing which author belongs to the user. Without a request/profile value, this can silently learn and reproduce another contributor's voice; require confirmation instead of inferring identity.

[Copilot]

Copilot review overview

🟡 Changes recommended

Conflicting front-matter guidance, incomplete sample handling, and potentially sensitive saved paths need correction.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1

Open (1)

• Redact private and machine-specific sample locations · New

Resolved since last review (1)

• Fix apostrophes breaking single-quoted YAML scalars

Previously missed (2)

In code that hasn't changed since last review

Handle all cases with fewer than three samples

skills/​make-blog-post/​SKILL.md:52

This only handles the zero-sample case, but the workflow requires three to five samples and the reference says fewer than three gives a thin read (references/voice-profile.md:7). With one or two posts available, the skill neither asks for enough additional samples nor discloses that the match is limited. Handle every <3 case explicitly so a thin profile is not presented as a full voice match.

Avoid raw front matter for non-parsing destinations

skills/​make-blog-post/​SKILL.md:119

“No front matter contract” also includes Gists, Discussions, hosted editors, and other destinations that do not parse front matter. This fallback therefore conflicts with references/delivery.md:11-19, which says those targets must not receive raw front matter. Limit this template to destinations that actually parse YAML so venue output cannot expose metadata as body text.

[Copilot]

Copilot review overview

🟢 Approval recommended

The skill is coherent, differentiated, correctly registered, and has no unresolved review findings.

Review effort: Balanced
Findings: None

[github-actions]

🚦 Submission status: ⏳ Awaiting automation

Risk tier: merge-risk:medium — New or substantially changed resource without privileged execution
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access.

Why this tier

• Adds 6 file(s), e.g. skills/make-blog-post/SKILL.md
• Changes 455 lines (low-risk limit is 40)

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Skill validation	✅ Passed	Passed · logs
Skill lint (vally)	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	✅ Passed	Passed · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs
Contributor risk signal	🔧 Infrastructure failure	The contributor check succeeded but its result artifact was missing, unreadable, or for another commit · logs

Action needed

• 🔧 Contributor risk signal hit an automation problem that is not caused by your contribution. Comment /rerun-checks to retry; maintainers are notified if it keeps failing.

Review

• Approvals: 0/1
• Assigned reviewer: aaronpowell
• Review target date: not set
• Still needed: 1 more approval(s)
• No staffed reviewer pool owns these files yet; any reviewer with write access counts as the domain reviewer.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 96d3472 · gate run · This comment is maintained automatically — see submission gate docs.}

[Copilot]

Copilot review overview

🟡 Changes recommended

Remote repository destinations need an explicit local-checkout fallback to avoid an invalid or unintended delivery path.

Review effort: Balanced
Findings: 1

Open (1)

• Require a local checkout path for named repositories · New

[Copilot]

Copilot review overview

🟢 Approval recommended

The skill is complete, correctly registered, internally consistent, and has no unresolved review findings.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Require a local checkout path for named repositories