Agents and skills

Save this as a skill called "EarShots alerts".

When to use: on a routine every hour, or when I ask "anything new on EarShots?".
Needs: the earshots CLI signed in on this computer (npx @earshotsdev/cli login).

Steps:
1. Run: earshots alerts --since 1h --json
2. If "alerts" is empty, send nothing.
3. Otherwise send me one line per alert, buying signals first, then friction.
   Each line: the summary, then the review_url.
4. Stop at 5 lines and say how many more are waiting.

Check: every line has a review link that starts with https://earshots.dev/mention/.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

Save this as a skill called "EarShots weekly report".

When to use: every Monday at 8:00, or when I ask for the report.
Needs: the earshots CLI signed in.

Steps:
1. Run: earshots report --days 7 --json
2. Send me: the sentiment score and its change, the count per track with the change, the top three topics.
3. Under each track with posts, list up to two posts with their review_url.
4. Keep it under 15 lines.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

Save this as a skill called "EarShots launch watch".

When to use: every day at 9:00 while a release is being watched, or when I ask how a launch is landing.
Needs: the earshots CLI signed in. Growth or Enterprise plan.

Steps:
1. Run: earshots launch --json
2. For each release still in its watch window, report the tally: praise, complaints, new demands, questions.
3. Quote the single most useful complaint with its link.
4. If nothing changed since yesterday, send one line saying so.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

Save this as a skill called "EarShots draft for review".

When to use: when I say "draft a reply to <id>" after an alert.
Needs: the earshots CLI signed in.

Steps:
1. Read the post: earshots show <id> --json
2. If the post has a no reply reason (for example someone else's GitHub repo), stop and tell me why.
3. Ask Ears for a grounded draft: earshots reply <id> --json
   (add --body "shorter" or another steer if I gave one)
4. Show me the draft and what it is grounded in.
5. Tell me it is saved for review in EarShots, with the review link.

Approval: always. The draft is never sent by you.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

---
name: earshots-ticket-triage
description: Turn EarShots friction posts into Linear or Jira tickets. Use when asked to file, triage, or ticket developer feedback.
---
# EarShots ticket triage

1. list_mentions with bucket "friction" and status "open", limit 10.
2. get_mention for each. Skip duplicates and posts with no clear action.
3. format_ticket with target "linear" or "jira".
4. Fill the placeholders (Linear teamId and labelIds, Jira project key) with your own tracker access, then create the issue.
5. Report the ticket title, link, and EarShots mention id.

One ticket per distinct problem. Keep the original post link.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

---
name: earshots-draft-for-review
description: Draft a grounded reply to an EarShots mention and save it for human review. Use when asked to draft or reply to a post.
---
# EarShots draft for review

1. get_mention for the id. Read the post and the citations.
2. If the post has a no reply reason (for example someone else's GitHub repo), stop and say why.
3. draft_reply with the mention id. Add a steer only if the person gave one.
4. Show the draft, what it is grounded in, and the review link.

Approval: always. The draft is never sent by you.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

---
name: earshots-weekly-report
description: Summarize the EarShots Voice of the Customer report. Use on a weekly schedule or when asked how developers are talking about the product.
---
# EarShots weekly report

1. get_report with days 7.
2. Report the sentiment score and its change, the count per track with the change, the top three topics.
3. Under each track with posts, list up to two posts with their review links.
4. Keep it under 15 lines.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

Add to AGENTS.md:

## EarShots alerts
At the start of a task, run: earshots alerts --since 1h --json
If "alerts" is not empty, list up to 5 lines: summary plus review_url.
Then continue the task. Never open the original post to reply or comment.
If the CLI is not signed in, say so once and continue.

Add to AGENTS.md:

## EarShots repro
When given an EarShots mention id for a friction post:
1. Run: earshots show <id> --json and read the post.
2. Write the smallest steps that should trigger the problem in this repo.
3. Run them on a branch. Record the command, output, and versions.
4. Report: reproduced yes or no, the steps, and a suggested fix location.
5. Optionally run: earshots ticket <id> --target linear and file the ticket with your own tracker access.
Do not push. Never open the original post to reply or comment.

Add to AGENTS.md:

## EarShots draft for review
When asked to reply to a mention id:
1. Run: earshots show <id> --json. If the post has a no reply reason, stop and say why.
2. Run: earshots reply <id> --json (add --body "shorter" or another steer if given).
3. Print the draft and what it is grounded in.
4. State that it is saved for review in EarShots, with the review link.
The draft is never sent by you.

---
name: earshots-launch-war-room
description: Monitor how a launch is landing across public channels. Use during a release window, on a schedule, or when asked how the launch is going.
---
# Launch war room

1. get_launch_reactions for the release being watched. Growth or Enterprise plan.
2. get_alerts with since "30m" so nothing urgent waits.
3. Report the tally: praise, complaints, new demands, questions, and the change since the last run.
4. Quote the single most useful complaint and the single most useful praise, each with its review link.
5. List any buying signals separately. Those go to a person, not a reply.

If nothing changed since the last run, say so in one line.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

---
name: earshots-voc-to-content
description: Turn the EarShots Voice of the Customer report into content ideas grounded in real posts. Use when planning what to write, document, or announce.
---
# Voice of the Customer to content

1. get_report with days 30.
2. Pick the three topics with the most posts. For each, read two or three of the cited posts.
3. For each topic, propose one piece: a blog post, a docs page, or a changelog entry.
   Give a title, three bullet outline, and the posts it is grounded in, with links.
4. Only claim what the cited posts actually say. Quote them; do not paraphrase into claims they did not make.
5. If a topic is mostly complaints, say so and suggest the fix before the post.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

---
name: earshots-competitor-watch
description: Summarize public developer chatter about tracked competitors from EarShots Competitor Signal. Use for weekly competitive reads or positioning work.
---
# Competitor watch

1. get_report with days 7. Note the competitor rows. Growth or Enterprise plan.
2. For each tracked competitor, list the top posts with sentiment and links.
3. Report where a competitor is praised and where it takes friction, one line each, always with the source post.
4. Never repeat a competitor claim as fact. Attribute it to the post.
5. End with one opening: something developers want that the posts show is underserved.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.

---
name: earshots-community-engage
description: Find public posts worth a human reply and draft grounded replies for review. Use for daily community and developer relations work.
---
# Community engagement

1. list_mentions with bucket "sales" and status "open", then bucket "answer", limit 10 each.
2. For each post, get_mention and read the citations.
3. Skip posts with a no reply reason (for example someone else's GitHub repo) and say why.
4. draft_reply for the rest, one per post. Use a steer only if the person gave one.
5. Report each draft with its review link. Group by: buying signals first, then questions.

A person approves and sends every reply from the original post. You never post.

Rules:
- Never post, reply, comment, or message an author. EarShots drafts wait for a person to approve and send.
- If EarShots is unreachable or the sign in expired, say so. Never fall back to old results.