uplika/uplika-plugin / skills/voice-profile
voice-profile
VerifiedCreate or update the voice file the writing skills read: tone, ending style, words to avoid, signature, examples from recent posts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
| references/voice-template.md | markdown | 1.2 KB |
SKILL.md
View on GitHub---
name: voice-profile
description: "Create or update the voice file the writing skills read: tone, ending style, words to avoid, signature, examples from recent posts."
---
# Voice profile
Every writing skill in this plugin reads one file before it writes: `~/.uplika/<workspace-slug>/voice.md`. One file per workspace, because a workspace is one brand. Claude Code, Codex and the other agents all read the same path, so the voice stays the same whichever agent writes.
## When to use
- The person asks to set up or change how their posts should sound.
- A writing skill found no voice file and the person agreed to make one.
## Procedure
1. Find the workspace slug: `list_accounts` shows the workspace; if the account has several and the answer is `workspace_required`, ask which one and pass that `workspaceId` on every later call in this session.
2. If the file exists, read it and ask what to change. Otherwise start from `references/voice-template.md`.
3. Ask three questions first, in the person's language: the tone (two or three words), how posts usually end, and words they never use. Then the optional ones: who they talk to, what they will not claim, their signature (hashtags, sign-off, links).
4. Pull examples from what they actually wrote: call `list_channel_posts` for their main channel and take three to five recent posts (their best ones if they say which). Paste them as they are; do not rewrite them.
5. Show the whole file and save it only after they approve. Create the folder if needed.
## Agents that cannot write files
Keep the profile in the conversation for this session only and say so. Offer the text so the person can save it themselves.
## Tools
- `list_accounts`: which workspace (slug) the file belongs to
- `list_channel_posts`: the person's own recent posts as examples
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |