2,787 件 ・ 関連度順
概要と使いどころ
Run the Definition of Done checklist for the current wp-rocket branch and report PASS/WARN/FAIL with evidence. Two modes: layer 1 (self-correction inside backend-agent / frontend-agent — resolves FAILs before handoff) and layer 2 (independent orchestrator gate — fresh perspective after handoff). Pass layer: "1" or layer: "2" when invoking.
日本語の概要は準備中です。原文の説明を表示しています。
Build prospect lists where the prospect is already one hop from the client, and write the line that says so. Seven members, each with its own source. Current-customer alumni is the priority member - everyone who ever worked at one of the client's customers or case-study companies and has since moved on. Triggers on "warm intro", "who do we know at that account", "they used to work at our customer", "alumni of our case study company", "shared investor angle", "who is in the same city as our rep", "did they visit our site". Outputs warm_intro_line plus a per-member evidence column.
日本語の概要は準備中です。原文の説明を表示しています。
Checks whether a company's own website mentions a specific keyword, using one simple Google site: query per keyword through a SERP API, and turns the hit into a copy-ready line. Triggers on "does their site mention X", "site: search", "find companies whose website says X", "filter this list by a keyword on their site", "check if they talk about X", "google search enrichment". Outputs site_keyword_hit plus a one-clause personalization line with an evidence URL.
日本語の概要は準備中です。原文の説明を表示しています。
Decides which named technologies a company actually runs on its website, verified against the live site. Triggers on "find companies using Shopify", "they're on HubSpot", "tech stack targeting", "technographics", "who uses Klaviyo", "companies running WordPress". Outputs a per-domain verdict (tech_confirmed plus the verified stack and its evidence); the copy-ready clause is OFF by default and runs only when the operator asks for one.
日本語の概要は準備中です。原文の説明を表示しています。
Work with the opt-in codex-on-crack build panel. Report registered run and review status, submit new screenshot evidence for a registered review, and send the user to the panel to decide. Never record user feedback or visual approval yourself.
日本語の概要は準備中です。原文の説明を表示しています。
Use real run evidence, validation failures, source drift, platform drift, and user feedback to plan and, only after explicit approval, apply structural upgrades to an existing skill. Use when the user asks to improve an existing skill from recent runs, recurring failures, outdated sources, excessive bloat, changed platform behavior, or validated workflow feedback. Do not use to create a brand-new skill or to execute the business workflow itself.
日本語の概要は準備中です。原文の説明を表示しています。
Draft, audit, or minimally revise English- or Chinese-language academic prose to reduce formulaic, vacuous, mechanically repetitive, or process-leaking language while preserving claims, evidence strength, logical relations, manuscript-wide terminology identity, document-level pattern variation, and scholarly register. Use for papers, abstracts, grants, cover letters, and reviewer responses when the user asks to de-AI, humanize, audit AI-like phrasing, or rewrite text without changing meaning. English is primary; Chinese is supported. Not for detector evasion, policy circumvention, pure translation, non-academic copy, or adding facts, citations, examples, or author experiences that the source does not contain.
日本語の概要は準備中です。原文の説明を表示しています。
Repo-local workflow skill for large coding tasks. Initializes .agent/tasks/TASK_ID artifacts, installs project-scoped Codex and Claude subagents, updates AGENTS.md plus the repo's Claude guide file with the workflow, and runs a spec-freeze → build → evidence → verify → fix loop with fresh-session verification.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, triage, and write academic rebuttals and review responses. Use when an AI research agent needs to handle conference, journal, workshop, or grant reviews; classify reviewer concerns; decide what evidence or experiments can change the decision; write an AC-facing executive summary; draft per-reviewer responses; correct factual misunderstandings without sounding hostile; handle novelty, baseline, method, experiment, clarity, and scope objections; or produce a final rebuttal checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Plug-in web search, X (Twitter) search, and page fetch for models without native web access. Use whenever the task needs current information, external facts, source links, posts from X, or the content of a specific URL, and the active model/harness has no native search or fetch tool. Runs the modsearch CLI to return structured JSON evidence. Also use when the user asks how to install or configure modsearch, or wants to switch engines or add a key.
日本語の概要は準備中です。原文の説明を表示しています。
只读查询 easyeda-agent 仓库的工具能力、实现、参数化样例与验证证据，适合在其他项目中复用 EDA 自动化经验。 Search the linked easyeda-agent checkout for capabilities, implementation, examples, and evidence; does not operate an EDA document.
日本語の概要は準備中です。原文の説明を表示しています。
Search an index of public repositories, GitHub issues, merged pull requests, repository READMEs, and curated documentation sites. Use when a programming question needs external documentation or upstream evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve the prompt surface of Avibe Agents across backends (Claude, Codex/GPT, OpenCode) — global and project rules, Agent system prompts, Skills, delegation briefs, and Task and Watch messages — using real run evidence. Use when an Agent misbehaves (stalls, over-asks, over-reaches, ignores or over-applies a rule), after a model or backend change, or when the user asks to review, clean up, or tighten prompts.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized digital forensics including memory dumps, disk timelines, PCAP investigation, artifact triage, and IR evidence preservation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when running, reviewing or changing coco's self-evolution cycle: the 30-day loop that observes how skills are actually used, proposes evidence-backed edits to them as one branch and one pull request, and lands nothing without the owner's merge. Also use when asked why a skill changed, what the loop would propose next, or how to reject a proposal so it is not raised again.
日本語の概要は準備中です。原文の説明を表示しています。
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
日本語の概要は準備中です。原文の説明を表示しています。
Monthly, file work only, no browser at all. Re-reads a month of real change outcomes and rewrites the file that decides what the fix runner may change without asking first. A class the member merged unchanged repeatedly widens by exactly one step. A class they edited, closed unmerged, or that regressed narrows immediately. It never touches the outer boundary, which no volume of evidence can widen.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Runs once by hand on the first day and once a month after that, on the first weekday, light browser lane. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the pipeline, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed to the files it owns, and carries every member written setting across verbatim. It holds every outbound action unless you released the channel, and it never enters a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the launch board, builds the tailored command center, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed, reconciles drift, and rebuilds. It holds every outbound action unless you released the channel, and it never enters 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.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, browser only when a source refuses to be fetched. Counts unpublished calendar entries per property by folding the published ledger against the calendar, and where every property is above its runway threshold it records the counts and exits, which is the normal run. Where a property is low it researches the next block from rank evidence, the topic map, and live result sets, refuses any keyword already targeted, and appends fully specified entries after the last existing block. It is the only writer of the calendar and it never modifies, reorders, or renumbers an existing entry.
日本語の概要は準備中です。原文の説明を表示しています。