66 个 · 按相关度排序
Weekdays, heavy browser lane. Selects the qualified people who have never been written to, drafts each one a first touch into a dated queue file the member reads, and composes each passing draft into the member's own mailbox as an unsent draft. It verifies by the Drafts count and never by a toast. It holds every outbound action unless you released the channel, and it never touches a credential.
中文简介正在准备中。当前显示原文说明。
SEO/GEO Agent Operations SOP v2 — Rebuilt from real-world operations (analook.com 0→launch, GSC incident, DataForSEO monitoring, gingiris.tools post-migration recovery). What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily SEO log — first item is always GSC token status check • Data cross-validation rule: any external metric must come from ≥2 sources before use • Backlink progress tracking (6-week wait → check → alert if not indexed) • New vs. established site strategy matrix (new site <6mo: KD≤20; mature: KD up to 35+) Real incidents baked in: GSC token expired silently for 2 weeks (analook.com), P0 keywords dropped out of Top 100 after domain migration (gingiris.tools), traffic data off by 17× from single-source DataForSEO. Triggers: "SEO agent" | "SEO daily report" | "GSC monitoring" | "DataForSEO" | "GEO agent" | "backlink tracking" | "IndexNow" | "competitor comparison page" | "SEO SOP" | "autonomous SEO" | "GEO triple combo" 🇨🇳 SEO/GEO Agent 运营 SOP v2 — 基于真实运营经验重写（analook.com 从零建站 + GSC 断档 2 周 + DataForSEO 监控 + gingiris.tools 迁移权重恢复）。 对话式开局、强制日报（GSC token 是第一项）、数据交叉验证铁律、外链进度追踪、新老站区分策略。
中文简介正在准备中。当前显示原文说明。
Run the oncall handoff for a rotation window — the whole handoff, not just a document: build the summary (what the incoming oncall needs first, what's still open, incidents with impact numbers, alert and page counts, hygiene suggestions, every number traceable to a source), post it for the outgoing oncall to correct, walk the incoming oncall through the open items in the thread, update the list as they respond, and note when they acknowledge. Runs mainly in the team's standing oncall / monitoring channel, normally as a scheduled routine firing at rotation change so the report is waiting when the shift turns over; can also be run by hand and works from an incident channel. Use when a handoff routine fires, or on "handoff", "hand over", "oncall summary", "weekly oncall report", "what happened this shift / this week". Re-running for the same window updates the report rather than duplicating it. Unattended runs carry a run-summary block and at least one chart.
中文简介正在准备中。当前显示原文说明。
Generate the ≤10-minute Loom walkthrough script for a completed Weekly Community Signal report — a plain spoken briefing that dives straight into what the team needs to know, walking the report top to bottom (CopilotKit page first, then AG-UI in the same order). Straightforward and factual, NOT a radio show or a performance; no hype opener, no blame framing. Runs after every report (invoked by weekly-report) and on "loom script", "walkthrough script", "record the loom", "narrate the report".
中文简介正在准备中。当前显示原文说明。
Compose a newsletter draft from Ahmad's OpenMark bookmarks. Use whenever Ahmad asks to draft, compose, write, or assemble a newsletter — phrases like "write me a newsletter on X", "make a newsletter about Y", "newsletter draft on Z", "put together a newsletter about W", "compose a newsletter", "draft my newsletter". Also use when Ahmad asks for a weekly write-up, roundup, or curated post. Pulls from OpenMark first, then WebFetches the chosen sources for quote-grade detail. Triggers on "newsletter", "draft a newsletter", "compose", "roundup", "weekly post", "curated post".
中文简介正在准备中。当前显示原文说明。
Launch new products from idea to first customers. Use when launching products, finding early adopters, building launch week playbooks, diagnosing why adoption stalls, or learning that press coverage does not equal growth. Includes the three-layer diagnosis, the 2-week experiment cycle, and the launch that got 50K impressions and 12 signups.
中文简介正在准备中。当前显示原文说明。
Create and maintain Paperclip status cards for work you want to track. Turn a plain-language request into focused task searches, produce an initial summary, and update reports using the changes or snapshots supplied to the assigned run.
中文简介正在准备中。当前显示英语简介。
Plan a small SaaS business, from checking demand to launching an initial product. The skill helps define an MVP, a first version with only essential features, choose pricing, organize launch tasks, and consider customer acquisition and retention.
中文简介正在准备中。当前显示英语简介。
Plan paid advertising across Google Ads, Meta, LinkedIn, and other platforms. Build campaign structures, ad copy, audience plans, and budgets, then use performance metrics and account checks to identify practical improvements.
中文简介正在准备中。当前显示英语简介。
Set up Loop Engineering through a single command-line tool, choosing a workflow pattern and agent tool. Start in report-only mode, check setup health and readiness, and provide next actions and first-run instructions.
中文简介正在准备中。当前显示英语简介。
Prepare semester-end handoff memos for legal clinic cases using deadlines, case history, and client communication logs. Produce individual case records and a cohort summary covering ownership transitions, unassigned cases, and priorities for incoming students.
中文简介正在准备中。当前显示英语简介。
Monitors task execution for skill improvement opportunities: logs patterns, user corrections and methodology worth preserving to the workspace, turns them into skill updates in a weekly review, and flags repeating work as new skills. Use during ANY multi-step task, agentic workflow, or work session. Also triggers in post-task feedback discussions and when the user mentions skill observations, the observation log, or skill taxonomy. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: invoke this skill before the FIRST tool call of any session and before writing or proposing a plan — any turn that will involve a tool call counts. This sentence is the session-start trigger and the only activation layer that survives an unreachable config file; pair it with a CLAUDE.md instruction or a session-start hook (references/environments.md). A subagent dispatched by a session already running it does not run it: it writes nothing and puts its findings in its report.
中文简介正在准备中。当前显示原文说明。
Use when the user asks to "build our social posting calendar", "set weekly slots and queue depth per channel", or "plan the evergreen recycle rotation"; produces the always-on brand calendar — pillar allocation with hero/hub/help balance and give:ask targets (all labeled Estimated starting heuristics to calibrate against own analytics, never scored rules), per-channel recurring slots with queue depth, a batching workflow, an evergreen recycle cycle with freshness re-checks, deliberate open slots for realtime/trend moments fed by trend-spotter go/skip verdicts, and first-comment/publish-order ops — cadence commitments filed to the channel registry, and no batch ships to the queue without a SHIP verdict from social-quality-auditor pre-publish mode. Not for repurposing an existing asset or the paid-amplification calendar — use content-amplifier. 社媒排期/内容日历/栏目配比/常青循环复用
中文简介正在准备中。当前显示原文说明。
Write status updates people actually read — the traffic-light-plus-narrative format (state first, story second), the blockers-are-asks rule, and the skimmable structure that respects a reader with thirty seconds. Use when asked write my weekly update, format our team's status posts, nobody reads my updates, or what goes in a good async check-in. Produces the update format with a filled example, the blockers-as-asks discipline, and the reader-time contract.
中文简介正在准备中。当前显示原文说明。
Weekly. Works dependency and supply chain debt one project at a time, sorting every candidate into patch and lockfile only, minor, and anything major or breaking. It bumps the first class on a branch behind that project's own gate and pushes it for the member to merge. It holds the other two with a reason and a card carrying the evidence, so the member decides rather than being handed a red build.
中文简介正在准备中。当前显示原文说明。
Weekdays, file work only, no browser at all. Reads every ledger and run record since its cursor, resolves which drafted changes actually merged by reading the commit graph rather than a dashboard, closes and reopens incidents on that evidence, folds the card inbox, re-renders the review board, and writes the short morning brief the member opens first. It never merges, never deploys, and never touches a credential.
中文简介正在准备中。当前显示原文说明。
Weekdays. Takes the one card the standup marked next and turns it into a reviewable change on a branch, never a deployment. It reads the project's own rules and docs first, makes the smallest change the card describes, runs that project's own gate, writes a change brief with the rollback in one line, and pushes the branch for the member to merge. It never merges, never deploys, never applies a migration, and never rotates a key.
中文简介正在准备中。当前显示原文说明。
Weekdays, file work only, no browser at all. Reads every run record since it last ran, folds the published, draft, indexing, and rank ledgers, folds the card inbox into the work board, marks the single card the draft run works today, and writes the short morning brief the member opens first. It holds publishing and spending unless you released the channel, and it never touches a credential.
中文简介正在准备中。当前显示原文说明。
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, file work only, no browser at all. Takes the single highest ranked open fault on the fleet and turns it into something the member can act on in a minute: the fault in one sentence, the first record that shows it, what changed around that date, three ranked causes each with its evidence line, what the failure has cost, and one paste ready correction line with the exact path it belongs in. It reads other Employees strictly read only, writes nothing outside its own folder, sends only where you released the channel, spends only where you released it, and never touches a credential.
中文简介正在准备中。当前显示原文说明。
Weekdays. Turns the contactable people in the signal ledger into today's due first touches and follow ups, written into dated queue files the member reads, edits, and sends by hand, and optionally into the member's own mailbox as unsent drafts. It holds every outbound action unless you released the channel, and it never touches a credential.
中文简介正在准备中。当前显示原文说明。
Weekdays, file work only, no browser at all. Reads every ledger, queue file, and run record written since its own cursors, turns the member's ticks into sent rows and closed cards, folds the card inbox, re-renders the pipeline board, and writes the short morning brief the member opens first. It names the veto window every day. It holds every outbound action unless you released the channel, and it never touches a credential.
中文简介正在准备中。当前显示原文说明。
Weekdays, file work only, no browser at all. Walks every AI Employee installed on this machine, reads each one's own run log strictly read only, classifies every routine as running, stopped loudly, stopped silently, or paused, ages the faults, folds the decision register, and writes the one short brief the member opens first. It never writes into another Employee's folder, sends only where you released the channel, spends only where you released it, and never touches a credential.
中文简介正在准备中。当前显示原文说明。
Weekdays, file work only, no browser at all. Reads every ledger, queue file, and run record, turns yesterday's ticks into facts a machine can count, folds the slot inbox, rewrites the content calendar, and writes the one short brief the member opens first. Its most important line names which slots publish today and how to stop them. It publishes only where you released the channel, never replies, spends only where you released it, and never touches a credential.
中文简介正在准备中。当前显示原文说明。