Skip to content

gooseworks-ai/goose-skills / skills/marketing/voice-card

voice-card

Verified

Builds or updates a voice card from a company blog ("extract our blog voice") or how an account or person actually writes, measured from about 8 or more of their real posts (length, casing, emoji, openings, pet phrases, opinions with their source). When there are too few posts, it runs a short interview instead. It ends with a test that checks a draft against the card. The brand's rules always beat the card. Use alone when you already have the account's posts or the person on hand; otherwise run the playbook for the job (e.g. run-organic-social, write-outreach, email-lifecycle).

FileKindSize
SKILL.mdskill md6.9 KB
references/blog-voice.mdmarkdown4.7 KB
skill.meta.jsonconfig655 B
tests/examples/2026-10-22/blog-voice.mdmarkdown7.1 KB
tests/fixtures/company-blog.mdmarkdown6.8 KB
tests/test-by-hand.mdmarkdown2.4 KB

tests/fixtures/company-blog.md

View on GitHub
# Company blog fixture

Five complete short articles for fictional Papertrail. All text is original test material. URLs use the reserved example domain; no live fetch is expected. Brand rules: plain language, retain human approval, no measured time-saved claim. Owner has not confirmed this guide.

<!-- article:1 -->
# Name the exception before you route it
Source: https://papertrail.example/blog/article-1
Author: Mira Patel (company staff, supplied metadata) · Published: 2026-10-01 · Retrieved: 2026-10-22

An invoice arrives with a price nobody recognises. The first question is small: which line needs a decision? Write that down before you ask three people to review the whole invoice. A clear exception is easier to hand over than a vague request to take a look.

## Give the reviewer a question
Keep the invoice number, disputed line and reason together. A reviewer needs enough context to answer that question. They do not need a second copy of every message about the supplier. If two lines have different problems, give each its own explanation.

## Leave the decision where it can be found
Once someone answers, keep their decision beside the original question. Record who answered and when. The next person should be able to follow the sequence without guessing which email contains the final answer. A decision with no link to the question is another loose note.

## Keep the approval step
Reviewing an exception is not the same as approving a payment. Keep the approval that your team already uses. The review record supplies context for it. It should not quietly replace it with a different decision.

See how the shared review queue works.

<!-- article:2 -->
# An export needs a reader
Source: https://papertrail.example/blog/article-2
Author: Mira Patel (company staff, supplied metadata) · Published: 2026-10-03 · Retrieved: 2026-10-22

A spreadsheet export is useful when someone can tell what its rows mean. Before adding another column, name the person who will read it. A controller reviewing a month needs a different view from a teammate picking up one disputed invoice. Start with that difference.

## Name the row
Each row should describe one event or one decision. Mixing invoice totals with reviewer actions makes the sheet harder to interpret. Put a clear heading on each column. If a heading needs a spoken explanation every month, write the explanation beside the export.

## Keep the source close
A decision should point back to the invoice and the question it answered. The reader can then check the original context. Without that link, a tidy sheet can still leave them unsure what happened. The file is a record, not independent proof that the decision was right.

## Test the handover
Give the export to the person who needs it. Ask them to find a decision and explain the row in their own words. Their questions tell you what to clarify. Keep the test small enough to repeat when the headings change.

See the review-history export.

<!-- article:3 -->
# What a handover note should hold
Source: https://papertrail.example/blog/article-3
Author: Jon Ellis (company staff, supplied metadata) · Published: 2026-10-05 · Retrieved: 2026-10-22

A teammate picks up an invoice after lunch. They can see the amount, but not why the supplier is waiting. The missing part is the question that paused the work. A handover note should make that question visible before it tells the next person what to do.

## Say what is unresolved
Write the disputed item and what you still need to know. Separate a confirmed fact from a guess. If the supplier has not replied, say that. An empty field leaves the next person to decide whether nobody checked or nothing was found.

## Name the next decision
State what answer would let the work continue. Avoid asking someone to review everything when only one line is disputed. The note should narrow the question without deciding it for them. Keep the relevant invoice and earlier reviewer decision close enough to inspect.

## Close the loop
When the question is answered, record the answer in the same place. A new message can alert the team, but it should point to the record. The next handover then starts from the latest decision instead of a fresh search through chat.

See the shared review queue.

<!-- article:4 -->
# Keep a review separate from an approval
Source: https://papertrail.example/blog/article-4
Author: Jon Ellis (company staff, supplied metadata) · Published: 2026-10-07 · Retrieved: 2026-10-22

A review can explain why an invoice looks wrong. An approval decides whether the payment should move forward. Those jobs can involve the same person, but they ask different questions. Give each decision a name so the team knows which one has been made.

## Describe the review
A reviewer might confirm that a quantity matches the delivery or flag a price for discussion. That finding belongs beside the question and the source invoice. It gives the approver context. It does not by itself grant permission to make a payment.

## Keep the existing authority
If your team already has an approval process, describe how the review record enters it. Make the boundary visible to a new teammate. A tool that adds context should not quietly change who is allowed to approve. Write down any exception to that rule.

## Try one disputed invoice
Walk through one example with a reviewer and an approver. Ask each person which decision they own. If the answers overlap, clarify the boundary before adding more work. The point is to understand the handoff, not to invent a new approval system.

See how the review queue fits your process.

<!-- article:5 -->
# Read the record before changing the process
Source: https://papertrail.example/blog/article-5
Author: Mira Patel (company staff, supplied metadata) · Published: 2026-10-09 · Retrieved: 2026-10-22

A delayed invoice does not tell you why the work stopped. The record might show a missing receipt, a price question or a reviewer who never received the request. Read that sequence before deciding which part of the process needs to change. One delay can have several causes.

## Follow one question
Start with the original exception and read the decisions in order. Keep facts separate from explanations offered later. A recorded date can show when someone answered. It cannot tell you why they waited unless they wrote that reason down at the time.

## Look for a repeated problem
Compare a few similar exceptions. Name what they share and what differs. Three unanswered price questions might justify a closer look at supplier information. They do not prove that every delay has the same cause. Keep the scope of the observation visible.

## Change one part
Choose a small adjustment and decide what you will check afterwards. The next record should help you see whether the question became easier to answer. Keep the approval process in place while you test the review step. A clear test leaves room to change your mind.

See the review-history export.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall