daily-blog-draft
Skill0 starsChanged 6 months agoMITView on GitHub
Automated blog content pipeline. Research, write, generate images, create WordPress draft, and prepare social media versions overnight. Wake up to a complete content package ready to publish.
In this repository17 other files it gives its agents.
- blog-banner-creationSkill
- image-generationSkill
- script-to-speechSkill
- company-deep-diveSkill
- email-verificationSkill
- funnel-playbookSkill
- google-ads-auditSkill
- landing-page-funnelSkill
- linkedin-content-image-typesSkill
- viral-comment-strategySkill
- autonomous-task-reliabilitySkill
- build-your-brainSkill
- diagram-generatorSkill
- expert-councilSkill
- liaclSkill
- parallel-researchSkill
- rate-limit-safeguardsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Purpose: Create a complete blog content package overnight for review and publishing each morning.
- Distinctive: line 13
Trigger: Run during end-of-day automation or scheduled task.
- Distinctive: line 27
Write blog post in your brand's CEO/thought-leader voice
- Distinctive: line 38
Avoid: hands, fingers, faces (AI generation artifacts)
- Distinctive: line 52
Add engagement CTA ("What do you think?")
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Daily Blog Draft System
Purpose: Create a complete blog content package overnight for review and publishing each morning.
Trigger: Run during end-of-day automation or scheduled task.
OVERNIGHT WORKFLOW
Step 1: Research Phase
- Scan industry news, trends, and topics relevant to your niche
- Find an angle that ties to your brand philosophy
- Focus on fascination and insight, not just information
Step 2: Writing Phase (800-1200 words)
- Write blog post in your brand's CEO/thought-leader voice
- Strategic, visionary perspective
- Clear connection to your product or service
- Include CTA at end
Step 3: Image Generation
Requirements:
- Size: 1792 x 1024 (wide cinematic) or 1920 x 1080
- Include: brand name text, blog post title text, brand icon
- Style: Professional, modern, on-brand aesthetic
- Avoid: hands, fingers, faces (AI generation artifacts)
Step 4: CMS Draft
- Publish as DRAFT (not live)
- Set featured image
- Assign appropriate category
- Save markdown backup locally
Step 5: Social Media Versions
LinkedIn Newsletter Version:
- Adapt blog for LinkedIn article format
- Arrow formatting for lists
- Add engagement CTA ("What do you think?")
- Add subscribe prompt
LinkedIn Post Version (Short):
- 400-600 characters
- Hook + key insight + CTA
- Include blog URL
- Include relevant hashtags
Step 6: Notify Team
Send ALL deliverables:
- CMS edit link
- Blog image preview
- LinkedIn Newsletter file
- LinkedIn Post (copy-paste ready)
- One-line summary
MORNING DELIVERABLES
+------------------------------------------------------+
| MORNING CONTENT PACKAGE |
+------------------------------------------------------+
| |
| NEW BLOG DRAFT: [Title] |
| Edit: your-site.com/wp-admin/post.php?post=XXX |
| |
| [Featured image attached] |
| |
| LINKEDIN NEWSLETTER: [File attached] |
| |
| LINKEDIN POST (copy below): |
| [Ready-to-paste LinkedIn post] |
| |
| Category: [Topic Category] |
| Word count: ~1,100 |
+------------------------------------------------------+MORNING REVIEW WORKFLOW (5 min)
| Step | Action | Time |
| 1 | Open CMS edit link | 30s |
| 2 | Review draft, make any edits | 2 min |
| 3 | Click Publish | 10s |
| 4 | Open LinkedIn Newsletter file | 30s |
| 5 | Paste into LinkedIn Newsletter | 1 min |
| 6 | Click Publish | 10s |
| 7 | Copy LinkedIn Post text | 10s |
| 8 | Paste into LinkedIn feed post | 30s |
| 9 | Done | - |
IMAGE GENERATION PROMPT TEMPLATE
Professional blog header image for article titled "[TITLE]"
Visual requirements:
- Include text "[YOUR BRAND]" prominently
- Include the blog title "[TITLE]" as main text
- Include your brand icon/logo
- Dark background with on-brand color patterns
- Modern, professional, tech aesthetic
- Wide cinematic format (1792x1024)
IMPORTANT: NO HANDS, NO FINGERS, NO PEOPLE, NO FACES.
Abstract visualization only.
Style: High-end corporate blog, minimalist, premium feel.FILE ORGANIZATION
| Asset | Path Pattern |
| Blog drafts | content/blog-drafts/YYYY-MM-DD-slug.md |
| Blog images | content/blog-images/slug.png |
| LinkedIn newsletters | content/linkedin-newsletters/YYYY-MM-DD-slug.md |
| LinkedIn posts | content/linkedin-posts/YYYY-MM-DD-slug.txt |
QUALITY CHECKLIST
- Blog post is 800-1200 words
- Written in brand voice (not generic AI)
- Clear industry angle with original insight
- Featured image follows 75% safe zone rule
- CTA at end of blog post
- LinkedIn newsletter version adapted (not copy-pasted)
- LinkedIn short post is 400-600 characters
- All links are correct
- Category assigned
- Draft status (NOT published until reviewed)
Built by PureBrain -- AI-powered marketing operations.
Want the full suite of 183+ production-tested skills? Start your trial ->
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

