「raft」の検索結果

Review and revise academic papers with a senior-reviewer workflow. Use when an AI research/coding agent needs to work on an existing paper draft, PDF, LaTeX project, Word document, markdown manuscript, rejected paper, or paper idea that already has a concrete direction, and produce: paper maps, weakness audits, insight/novelty checks, reviewer objections, claim-experiment matrices, theory/proof checks, experiment plans, statistics/reproducibility audits, figure/table audits, ethics/compliance checks, revision plans, detailed section edits, or final submission checklists.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

公众号发布｜公众号草稿箱｜公众号群发｜图文推送｜微信 API｜wechat automation｜WeChat API automation｜auto publish｜scheduled publish — 公众号 API 发布工具，图文入草稿箱或直接群发，支持封面素材上传、发布前检查与 draft/published 模式切换。面向公众号运营、自动化内容团队、开发者。触发词：「发布」「提交」「群发」「推送」「发出去」「上传到公众号」「发到公众号」「可以发了吗」「发布前检查」。需要多环节串联（写+审+排+配图+发）请走 aws-wechat-article-main。

日本語の概要は準備中です。原文の説明を表示しています。

Step 4 of the PaperOrchestra pipeline (arXiv:2604.05018). ONE single multimodal LLM call that drafts the remaining paper sections (Abstract, Methodology, Experiments, Conclusion), extracts numeric values from experimental_log.md into LaTeX booktabs tables, splices the generated figures from Step 2, and merges everything into the template that already contains Intro + Related Work from Step 3. TRIGGER when the orchestrator delegates Step 4 or when the user asks to "write the methodology and experiments sections" or "fill in the rest of the paper".

日本語の概要は準備中です。原文の説明を表示しています。

Run the four paper-quality autoraters from PaperOrchestra (arXiv:2604.05018, App. F.3) — Citation F1 (P0/P1 partition + Precision/Recall/F1), Literature Review Quality (6-axis 0-100 with anti-inflation rules), SxS Overall Paper Quality (side-by-side), and SxS Literature Review Quality (side-by-side). TRIGGER when the user asks to "score this paper draft", "evaluate against the benchmark", "compare two papers", or "run the autoraters".

日本語の概要は準備中です。原文の説明を表示しています。

Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery/research, growth/metrics, design foundations/usability, design leadership/craft, UX/content, design systems, and a…

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, heavy browser lane. Captures the dated raw material tomorrow's drafts are built from, out of the member's own shipped work, their own site and changelog, their own signed in saved searches, and the places their audience already is. Every line carries a source URL read this run, a date, a verbatim quote, and an expiry. It invents nothing, it is read only everywhere and totally read only on LinkedIn, and it 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 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, 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. Opens the member's own signed in profile, post, and notification surfaces for every platform in the channel plan, confirms that everything published since the last run is genuinely live, reads the counts attached to each post, captures every comment, mention, quote, reply, and inbound message into a queue the member answers by hand, and drafts a suggested reply for each one. Read only everywhere and totally read only on LinkedIn. It sends only where you released the channel, never replies, 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.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly on a Wednesday, light browser lane. Turns the questions that keep coming back into the answer that only has to be written once. It reads the ticket ledger over the recurrence window, finds every theme that crossed its threshold, checks the member's own help center and the existing macros for an answer that already covers it, and writes a reusable macro and a help article draft for every theme that has neither. It publishes only where you released the channel an article, never edits a live help center page, sends only where you released the channel, spends only where you released it, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Test design mandate enforcement, test budget validation, TDD phase validation (3-phase canon per ADR-025), and external validity checks for the software crafter reviewer

日本語の概要は準備中です。原文の説明を表示しています。

Handle SLEAP GitHub support workflow for issues and discussions. Use when the user says "support", provides a GitHub issue/discussion number like "#2512", or asks to investigate a user report from talmolab/sleap. Scaffolds investigation folders, downloads posts with images, analyzes problems, and drafts friendly responses.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a leader must review or approve TEXT-based team output before it ships — content briefs checked for angle, pillar, and CTA, ad copy and creative checked for substantiated claims, on-brand tone, a hook inside the first 125 characters, and platform policy, ending in an Approve, Revise, or Redo verdict with point-by-point feedback. Trigger on 'review this brief', 'approve the ad copy', 'check ads before launch', 'review team output', 'is this good enough to publish', 'my team keeps sending me drafts'. Not for — reviewing a visual design, see `47-design-review-global`; evaluating a person over a period, see `65-team-performance-review-global`; writing the copy yourself, see `05-ad-copy-global`.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user needs to define, document, or enforce how the brand SOUNDS in writing — three personality traits, a five-dimension tone table, vocabulary to use, avoid, and ban, sentence rules, before and after rewrites, platform adaptation, and a copy approval checklist. Every content skill reads it before writing. Trigger on 'brand voice', 'tone of voice', 'voice guidelines', 'banned words list', 'this copy does not sound like us', 'every writer sounds different'. Also use when the user cannot say why a draft feels wrong. Not for — the visual side of brand, see `46-brand-guideline-global`; positioning and the message, see `58-positioning-global`; approving one specific piece, see `62-marketing-review-global`.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts formal explanation letters for Canadian Study Permit applications by structuring the argument around program attractiveness, background relevance, choice rationale, and family benefits.

日本語の概要は準備中です。原文の説明を表示しています。

Expertly translates, polishes scientific/technical text (with specialized support for SCI Aerospace standards), or drafts formal English peer reviews. Ensures accuracy, clarity, and adherence to high academic standards.

日本語の概要は準備中です。原文の説明を表示しています。

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Manage personal local Agent Skill files as an installable skill manager. Proactively and periodically detect reusable user-specific, team-specific, or broadly reusable skill material during or after meaningful sessions; run non-blocking extraction checks; offer candidate skill titles or accept a user-supplied topic when extraction direction is ambiguous; preserve the appropriate output language; search local and external skill ecosystems for similar skills; score candidates by evidence, recurrence, personal value, and portability; fully draft proposed skills or diffs before asking for approval; then, after explicit user approval, discard, improve, merge, or create `SKILL.md` folders.

日本語の概要は準備中です。原文の説明を表示しています。

Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.

日本語の概要は準備中です。原文の説明を表示しています。

Clarify a decision one question at a time and compare options against explicit criteria. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.

日本語の概要は準備中です。原文の説明を表示しています。