From fabrik
Interviews user one question at a time to clarify blog post angle, audience, evidence, scope, and tone before drafting. Activates on requests like 'write a post about X'.
npx claudepluginhub maragudk/fabrik --plugin fabrikThis skill uses the workspace's default tool permissions.
Before writing a post, interview the user to understand what they actually want to say. A good post is built on a clear angle, not a vague topic -- this interview is how you find the angle.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
Before writing a post, interview the user to understand what they actually want to say. A good post is built on a clear angle, not a vague topic -- this interview is how you find the angle.
Start by asking the user what the post is about. Then, depending on what comes back, work through some or all of these:
These aren't a checklist to march through. Pick what matters for the topic in front of you, and skip what's already obvious from the user's answers.
After the basics, bring pushback -- at your discretion, when the subject warrants it. A post that can't survive mild scrutiny during the interview won't survive publication. Examples of the kind of thing to probe:
Bring these questions honestly, not performatively. If the topic is a quiet, well-grounded how-to, you don't need to interrogate it. If the topic is a spicy opinion about an industry trend, you probably do.
Stop when you believe you could write a post that the user would recognize as theirs -- their angle, their voice, their evidence. Don't ask for permission to stop. Just write the post.