I have been using a small agent skill to turn Frontend Hire Open House posts into LinkedIn carousel PDFs.
The problem is simple: the Open House recaps are useful, but a blog post is not always the best format for distribution.
LinkedIn carousels work better for quick takeaways. They are easier to skim, easier to share, and better suited for people who are not already visiting the site.
The workflow problem
Creating these manually is annoying.
Every Open House post needs the same set of decisions:
- What should become a slide?
- Where should the page breaks go?
- Which claims deserve standalone treatment?
- How do we keep the Frontend Hire style consistent?
- How do we export the final PDF without redoing the same setup?
None of this is hard. But it is repetitive.
And repetitive work is exactly where agent skills are useful.
The skill
The skill lives at .agents/skills/frontend-hire-marp-open-house/.
It reads an Open House post, proposes slide breaks, waits for confirmation, generates a Marp deck, and exports a PDF.
The deck generation is powered by Marp, which makes it easy to write slides in Markdown and export them as PDFs.
The important part is not just the automation. It is the product constraint baked into the workflow.
The skill knows the expected output:
- A branded cover slide
- Clear page breaks
- Slide-friendly copy
- Consistent Frontend Hire styling
- A final PDF ready for LinkedIn
That means I do not have to rethink the format every time.
Why this matters
This turns one piece of content into two useful assets.
The original blog post remains the canonical recap.
The PDF carousel becomes the distribution asset.
That is the product value for me. I can spend more time improving the insight and less time doing layout work.
It also keeps the brand consistent without turning every post into a design task.
Small workflow, clear output, repeatable result.
That is exactly the kind of thing I want agents to handle.