5,179 件 ・ 関連度順
概要と使いどころ
Update/publish the Apache Tika website (tika-site SVN repo) for a release — step 17 of the Release Process. Handles the 4.x track (Changes page + aggregate javadoc + Antora docs branch) vs the 3.x maintenance track (full per-version apt docs + javadoc). Use for "update the site", "publish the site for X.Y.Z", "the website part of the release".
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to queue maintainer-accepted microsoft/apm issues (`status/accepted`) and fan them out through an isolated pool (default 2) of autopilot-issue-delivery-worker sessions. Any accepted type is eligible. Advisory `triage/recommended` is not authorization. Does not triage. Does not review PRs. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-*.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/*.schema.json), or the conformance fixture seed (tests/fixtures/spec-conformance/**). The panel fans out to four spec-ecosystem reviewers (swagger-openapi-editor, oci-distribution-editor, pkgmgr-registry-contract-editor, w3c-tag-architect), each running in its own agent thread, and a spec-editor synthesizer that produces a fold-now / defer-v0.1.1 / defer-v0.2 / reject list plus a ship decision keyed off a 1..10 shocked_meter scale. The orchestrator is the sole writer to the PR: ONE consolidated comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes folds, and renders a ship recommendation that the maintainer weighs.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. panel-mode (full | lean | delta) selects a surface-gated roster plus a CEO synthesizer; omitted or unknown mode is lean. Do not spawn inactive stubs. The orchestrator is the sole writer to the PR: ONE recommendation comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes follow-ups, and renders a ship-recommendation that the maintainer and author weigh.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain and patch existing Lark/Feishu documents while preserving comments, highlights, citations, and newer remote edits. Use for iterative document updates, local-mirror sync, or durable project ownership; LoopX integration is optional.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and manage guarded Codex App-native or launchd heartbeats for Codex main control threads. Use when the user wants Codex to periodically continue a specific thread only when it is idle, avoid interrupting active work, keep App-visible interactions, inspect thread status, or enable/disable project autopilot heartbeats.
日本語の概要は準備中です。原文の説明を表示しています。
Locate and read a Codex thread by a codex thread link, thread id, or rollout path across all local CODEX_HOME directories (~/.codex, ~/.codex-gpt, ...). Use when the user pastes a codex:// link, asks to understand the 前因后果 of a Codex session, wants a timeline of what a long-running main thread did, or needs to search / export a past Codex conversation.
日本語の概要は準備中です。原文の説明を表示しています。
Iterative diagnose-and-fix workflow that repeatedly uses the diagnose skill to find a proven problem, plan the smallest credible improvement, implement it, re-diagnose, and continue until no useful fix remains or user intervention is required. Requires the diagnose skill; selected installs must also install diagnose. Use when asked to keep debugging, fix and verify, iterate until satisfied, improve after diagnosis, or run a diagnosis/fix/verification loop.
日本語の概要は準備中です。原文の説明を表示しています。
Build, refactor, or review macOS menubar apps that use Tuist and SwiftUI. Use when creating or maintaining LSUIElement menubar utilities, defining Tuist targets/manifests, implementing model-client-store-view architecture, adding script-based launch flows, or validating reliable local build/run behavior without Xcode-first workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file. Concrete actions include adding Sendable conformance, applying @MainActor annotations, resolving actor isolation warnings, fixing data race diagnostics, and migrating completion handlers to async/await.
日本語の概要は準備中です。原文の説明を表示しています。
Build, validate, release, inspect, query, roll back, or archive a Marina application. Maintained source apps and uploaded applets use Postgres packages and marina release, independently of Marina runtime deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Design or revise a Marin experiment pipeline that binds reusable work into an artifact graph. Use for new workflow entrypoints, stage wiring, and pipeline placement decisions; use a narrower domain skill when it owns the launch.
日本語の概要は準備中です。原文の説明を表示しています。
Review an explicitly identified Marin pull request against the repository's correctness and maintainability expectations.
日本語の概要は準備中です。原文の説明を表示しています。
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main. Use for RL launch files, SkyRLRolePlan or SkyRLTopology changes, MarinSkyRL configuration, RL smoke tests, and requests to launch or relaunch RL on Iris.
日本語の概要は準備中です。原文の説明を表示しています。
Single-page SEO audit: content quality under Google's E-E-A-T framework and Helpful Content guidelines, on-page factors, search intent, technical signals and readability. Pulls GSC data for the page, crawls the live HTML, checks metadata, schema, internal linking and depth, and produces a scored report with fixes. Use whenever the user wants to analyze a specific page or URL, not the whole site. Trigger on: "analyze this page", "audit this URL", "how is this page doing", "evaluate my blog post", "check this landing page", "page SEO", "content quality check", "is this page good enough", "review this page's SEO", "what's wrong with this page", "how can I improve this page", "page analysis", "single page audit", "content audit for [URL]", or any request naming a specific URL/page for SEO evaluation. If the user provides a specific URL (not just a domain), this is likely the right skill; use /seo-analysis for full-site audits instead.
日本語の概要は準備中です。原文の説明を表示しています。
International / multilingual SEO audit focused on hreflang correctness: missing or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, hreflang vs canonical conflicts, and inconsistent signals across HTML head, HTTP headers and XML sitemap. Also reviews URL structure (ccTLD vs subdirectory vs subdomain), language targeting and geo signals. Use whenever the user runs a multi-language or multi-region site and asks about hreflang, international or multilingual SEO, the wrong-language page showing in search, or duplicate content across country versions. Trigger on: "hreflang", "international SEO", "multilingual SEO", "multi-region", "wrong language in Google", "x-default", "ccTLD vs subdirectory", "geo targeting", "language targeting", "my English page shows for Thai users", "th/en page ranking in the wrong country", or any cross-language/cross-country ranking question. For full-site audits use /seo-analysis; for a single URL use /seo-page.
日本語の概要は準備中です。原文の説明を表示しています。
TDD workflow for migrations - orchestrate agents, zero main context growth
日本語の概要は準備中です。原文の説明を表示しています。
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool call/result correlation, and common failure patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Recover deleted commits from GitHub using REST API, web interface, and git fetch. Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches. Includes techniques for accessing "deleted" commits that remain on GitHub servers.
日本語の概要は準備中です。原文の説明を表示しています。
Review tutti git diffs for project structure, layering, module ownership, and duplicate event-center infrastructure by planning focused architecture review tasks, then having the main agent orchestrate sub-agents for only the changed areas.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with @tutti-os/ui-system components, replacing local UI with shared components, querying component ids or metadata, promoting UI into shared base or business components, or maintaining UI-system storyboard inventory.
日本語の概要は準備中です。原文の説明を表示しています。
集中兵力：多件事同时争抢时间、注意力或预算时，列出全部待办，选定唯一主攻目标并公开锁定，彻底解决、验证后再转向下一个。当待办过多、推进分散、"每件都做了一点但都没做完"、需要决定先做什么时触发；只有一个任务、任务彼此独立可并行、用户明确要求同时推进时不触发。 English: Concentrate forces. When several tasks compete for time, attention, or budget, enumerate them, lock onto a single main target, finish and verify it completely, then move on. Trigger when priorities sprawl, effort is scattered, or you must decide what to do first; skip when there is one task, tasks are independent and parallel, or the user explicitly wants them advanced together.
日本語の概要は準備中です。原文の説明を表示しています。
调查研究：在下判断、做决策、给建议之前，先用第一手材料弄清现状，产出「事实 / 推断 / 未知」三栏调查结论。当上下文不完整、证据薄弱、领域陌生、用户说"先别动手"、或你发现自己在凭印象作答时触发；已充分调查后的执行阶段不要重复触发。 English: Investigate before judging. Gather firsthand facts and produce a fact / inference / unknown ledger before any recommendation. Trigger when context is incomplete, evidence is thin, the domain is unfamiliar, the user says "look first", or you notice yourself answering from impression; skip when investigation is already done and the task is pure execution.
日本語の概要は準備中です。原文の説明を表示しています。