Skip to content

uplika/uplika-plugin / skills/voice-profile

voice-profile

Verified

Create or update the voice file the writing skills read: tone, ending style, words to avoid, signature, examples from recent posts.

FileKindSize
SKILL.mdskill md1.8 KB
references/voice-template.mdmarkdown1.2 KB

references/voice-template.md

View on GitHub
# voice.md template

Adapted from Jakeschincariol/youtube-agent-skill `templates/voice.md` (MIT, license text in `THIRD_PARTY_LICENSES/youtube-agent-skill.MIT`). Not affiliated with the original author. Extended for every channel, not only YouTube.

Saved at `~/.uplika/<workspace-slug>/voice.md`, one file per workspace (brand). Every writing skill reads it.

```markdown
# Voice: <workspace or brand name>

## Who I am talking to
One person, described properly: who they are, what they already tried, what they want.

## Tone
Two or three words and one sentence on what that means here (for example: plain, warm, no hype).

## How I end posts
The closing habit: a question, a one-line summary, a call to action, nothing.

## Words I never use
The ones that are not mine ("unlock", "game-changer", "dive in", and so on).

## Words I do use
Phrases and habits that are mine. Keep them.

## What I will not claim
Numbers I cannot show, results that are not mine, tools I have not used.

## Signature
Hashtags, sign-off line, links that go at the end, if any. Per channel when they differ.

## Examples
Three to five of my own recent posts, pasted as they are (the best-performing ones if I know them).
```
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall