Build a reusable writing style profile from real posts, articles, emails, and product copy. Use it to keep social posts, outreach, and launch announcements consistent in tone, sentence rhythm, and expression across related writing tasks.
Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
Review the instructions the agent will receive before you install.
Build a durable voice profile from real source material, then use that profile everywhere instead of re-deriving style from scratch or defaulting to generic AI copy.
Use the strongest real source set available, in this order:
Do not use generic platform exemplars as source material.
x-api to pull recent original posts before drafting.Produce a reusable VOICE PROFILE block that downstream skills can consume directly. Use the schema in references/voice-profile-schema.md.
Keep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.
If the user wants Affaan / ECC voice and live sources are thin, start here unless newer source material overrides it:
Delete and rewrite any of these:
VOICE PROFILE across related tasks in the same session.Use this skill before or inside:
content-enginecrosspostlead-intelligenceIf another skill already has a partial voice capture section, this skill is the canonical source of truth.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.
Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.
Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.
Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.
Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.
Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.