sandhiveio/sandhive-cli / skills/sandhive
sandhive
VerifiedUse the SandHive CLI to turn verified project updates or news into X posts, find relevant conversations, and draft replies in the author's voice from original writing samples. Use for SandHive setup and drafting; publication stays manual.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.7 KB |
| agents/openai.yaml | config | 712 B |
| references/cli.md | markdown | 12.9 KB |
| references/draft-review.md | markdown | 4.1 KB |
| references/first-run.md | markdown | 3.6 KB |
| references/network-access.md | markdown | 9.3 KB |
| references/opportunity-triage.md | markdown | 5.3 KB |
| references/post-workflow.md | markdown | 5.3 KB |
| references/publication-registry.md | markdown | 3.9 KB |
| references/scheduling.md | markdown | 1.4 KB |
references/first-run.md
View on GitHub# First live batch
When the user requests setup with live API work authorized, carry the work through to a first batch of drafts in the same conversation. Do not stop at installation confirmation, a saved profile, a workflow menu, or a request to continue. Installing files by itself cannot start a conversation or authorize data submission. The installer prints a scoped live-run prompt for the user to review and send; a prompt merely printed by a tool is not user consent. Reuse authorization already given in the conversation. Installation-only, simulation, dry-run and local-only requests stay local to SandHive service execution; a simulation must not trigger live search, style retrieval or generation.
1. **Choose the project.** Use the user's named project; otherwise use the active project and its existing `.sandhive` profile, README, product docs and recent verified work. State the selected product and audience briefly. Do not ask the user to choose when the active project is clear. If several projects are equally plausible, prepare candidate context and ask only which one to use.
2. **Build the style locally first.** Reuse existing original writing samples or collect the user's own messages from accessible files and dialogue. Save at least three verbatim samples with source references and derive concise voice preferences. Do not ask for a separate human-authorship declaration. If local writing is insufficient and the intended account is known, retrieve candidates with `sandhive style`; ask only for an unrecoverable account or the missing samples after available sources are exhausted.
3. **Prepare the first batch.** Choose one evidenced post angle from completed work, or fresh relevant news when suitable work evidence is unavailable. Derive two or three concrete search phrases from the audience's problems, requests and workarounds. The supplied first-run prompt authorizes at most seven API requests: one optional style lookup, one search with up to 20 results, one post (one rewrite, or news generation then rewrite) and up to three replies, with one attempt each. A work update with local samples needs at most five requests. These are agent workflow limits, not server-enforced spending controls. Respect any narrower task, preview-only request, local-only preference or user-specified limits.
4. **Announce API use and execute within authorization.** Follow [network access and task scope](network-access.md), then run the required live CLI requests without another routine confirmation when this destination, data and work are already authorized. If they are not, prepare the selected inputs locally and ask one concrete permission question describing the destination, selected data and request limits. For posts, use the post workflow and publication registry. For replies, search, triage, obtain essential surrounding context where available, and generate replies to the ready candidates. Do not ask again whether to draft replies already included in the authorized batch. Continue independent parts when one item is blocked; never invent evidence, samples, updates or replies to meet a quota.
5. **Deliver drafts for review.** Show the selected project and voice basis briefly, the reviewed post, and each reviewed reply with its source link and a short reason it fits. Report empty results and blocked items honestly. Publication remains under the user's control. Save reusable context and the local draft registry.
Use up to three parallel workers for ready replies by default. Respect a current instruction or saved reply_concurrency preference. Suitable conversations may be absent; do not promise or fabricate a full batch.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |