221 件 ・ 関連度順
概要と使いどころ
Cut AI tells from text you write or edit for a human reader (commit messages, PR titles and bodies, docs, code comments, replies). Apply before committing, posting, or sending; leave prose you didn't touch alone.
日本語の概要は準備中です。原文の説明を表示しています。
Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow on macOS (Apple Mail, Calendar, Reminders). Powered by LMCP.
日本語の概要は準備中です。原文の説明を表示しています。
Send cold email and run outbound email campaigns from an agent with Sendsets. Connect or check sending mailboxes, turn a lead list (CSV or inline) into a multi-step email sequence with follow-ups, validate merge fields, send a test, launch, and read and answer replies. Use when the user asks to send cold emails, email a list of prospects or leads, run an outreach or outbound sequence, or follow up with contacts by email.
日本語の概要は準備中です。原文の説明を表示しています。
Use Sendsets to turn a software product into useful outbound campaigns, then operate mailboxes, warmup, campaigns, replies, and product integrations through the CLI. Use when the user asks to set up or run cold email with Sendsets or wants campaign ideas grounded in their codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Draft replies to YouTube comments in the creator's voice, triaged by which ones are worth answering. Use for "reply to my comments", "handle the comment section", "someone asked X", or a pasted comment thread.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload, anonymity requirements, statistician-reviewer pushback patterns, and decision-focused clarification strategy for theory-plus-experiments papers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing the response document for an Academy of Management Review (AMR) Revise & Resubmit — structuring point-by-point replies that show the theory was genuinely strengthened, not just defended. Drafts the response; revise the manuscript's theory FIRST (amr-theory-development / amr-data-analysis) before writing the letter.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting an ACM CCS rebuttal during the HotCRP author-response window, covering threat-model defenses, adaptive-attack objections, ethics and disclosure questions, anonymity constraints, adversarial reviewer pushback patterns, and decision-focused replies aimed at the meta-reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
Mine comments and replies on social posts, videos, and ads for recurring customer language, questions, objections, desired outcomes, complaints, product requests, purchase signals, and creative opportunities. Use for voice-of-customer research grounded in linked source evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Email campaign/sequence performance review composite. Pulls campaign data (sends, opens, replies, bounces), reads actual email copy and subject lines, analyzes reply content (objections, positive interest, questions), and produces a diagnostic report covering quantitative metrics, copy quality, lead quality, and actionable recommendations. Tool-agnostic — works with Smartlead (MCP), Instantly, Outreach, Lemlist, Apollo, or CSV data.
日本語の概要は準備中です。原文の説明を表示しています。
Research LinkedIn profiles and write personalized messages for any LinkedIn message type — connection requests, InMails, DMs, message requests, post comments, and comment replies. Takes LinkedIn URLs as input, researches each person (profile data + recent posts via Apify), and generates messages tailored to each lead's background, interests, and recent activity. Exports tool-ready CSVs for Dripify, Expandi, Botdog, PhantomBuster, or generic format. No LinkedIn cookies or login required.
日本語の概要は準備中です。原文の説明を表示しています。
Customer service on TikTok Shop — response time, dispute resolution, auto-replies, buyer satisfaction
日本語の概要は準備中です。原文の説明を表示しています。
Send Google Chat messages via incoming webhooks — text, rich cards (cardsV2), threaded replies. TypeScript types, card builder utility, widget reference inline. Use whenever the user wants to post to Google Chat from a script, build a chatbot reply, send a notification card, build a Google Chat webhook integration, or troubleshoot card / threading issues.
日本語の概要は準備中です。原文の説明を表示しています。
Write and optimize B2B cold email outreach sequences that get replies, covering personalization, follow-up cadence, deliverability, and compliance. Use when writing cold outreach, prospecting/SDR emails, or building outbound sequences.
日本語の概要は準備中です。原文の説明を表示しています。
When you or another skill needs to fetch the content of a social media post by URL — tweet, X thread, LinkedIn post, Instagram post, TikTok video, Bluesky post, Reddit thread, Mastodon status, Threads post, Hacker News thread. Returns normalized structured data (author, posted_at, text, engagement counts, media URLs, replies if requested) regardless of platform. Tries strategies in order: direct API (Bluesky, Mastodon, HN, Reddit), agent-browser with modal dismissal (LinkedIn, X preview), Wayback Machine (older posts), paid APIs (ScrapeCreators / Apify — only if env keys present). Triggers on "/social-fetch <url>," "fetch this tweet," "fetch this post," "what does this LinkedIn say," "read this thread," "pull this post." Used by deep-research (citing specific posts), jab-hook (inspiration account analysis), business-brainstorm (competitor / operator commentary).
日本語の概要は準備中です。原文の説明を表示しています。
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
日本語の概要は準備中です。原文の説明を表示しています。
Draft copy-paste-ready X replies - two options per reply-worthy tweet from tracked accounts, topics, or lists (default), or ready-to-post responses to engagement opps in recent logs (from-logs)
日本語の概要は準備中です。原文の説明を表示しています。
Daily GitHub notification inbox triage - surfaces aging vuln PR replies, security advisories, review requests, and mentions that need action
日本語の概要は準備中です。原文の説明を表示しています。
Find low-follower viral posts on X/Twitter for account-growth topic selection. Use when the user asks for X low-fan hits, Twitter low follower viral posts, 起号选题 from X, niche tweet inspiration, or viral posts ranked by author followers, views, bookmarks, likes, reposts, and replies.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, light browser lane. The one routine in this kit with an outward surface. Takes the slots that are due today, whose drafts were written yesterday and passed the copy check, whose hold box is not ticked, and whose destination the member wrote into the publish allow list themselves, and hands each one to the channel the member configured. It records a receipt the instant each slot lands. It never drives a browser control to publish, never replies, sends only where you released the channel a message, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, on a Friday, read only everywhere. Scores the week from the kit's own ledgers with a source path beside every number, cuts it by platform, framework, pillar, slot time, and post length, rewrites the drafting standards from that evidence and from nothing else, replays the browser flows the other routines depend on, and files exactly one thing to stop and one to do more of. It publishes only where you released the channel, never replies, spends only where you released it, never touches a credential, and never writes a number it did not measure.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, heavy browser lane, two halves in one run. First it reads the member's own mailbox for replies on the threads the ledger says were sent and records them. Only then does it work out who is due a follow up, write each one into a dated queue file, and compose it into the mailbox as an unsent draft. It holds every outbound action unless you released the channel, and it never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, heavy browser lane. Reads every support channel named in strategy/channels.md, meaning the mailbox, the helpdesk queue, the review and rating listings, the marketplace pages, and the forums where the member's products are discussed, and captures every new or changed item as one dated, sourced, severity graded line on the ticket ledger. It replies to nothing, reacts to nothing, marks nothing read or resolved, and takes no action of any kind on LinkedIn. It holds every outbound action unless you released the channel, and it never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。