本文へ移動
cccskills

「every」の検索結果

2,669 件 ・ 関連度順

概要と使いどころ

pr

無料

Open or update a pull request in this repository, including writing or rewriting its description. Use for every PR you create or edit here, and for /pr.

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

ccch1mneyyy/dsh-TUI4,6002026年10月14日 更新

Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, editing, or linting any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge*` tool call (`exec`, `search`, `write`, `edit`, `lint`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.

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

inkeep/open-knowledge4,5782026年10月15日 更新

Generates a plain English summary of everything that happened across all your accounts this week. What improved, what declined, what needs immediate attention, and what to prioritize next week. The Monday morning briefing that saves you an hour of pulling reports and context-switching between platforms. Platform: Google and Meta.

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

irinabuht12-oss/marketing-skills4,5622026年10月13日 更新

Takes your raw campaign performance data and writes the executive summary paragraph that goes at the top of the report. The plain English explanation of what happened, why it happened, and what's being done about it. The part every client actually reads. Platform: Google and Meta.

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

irinabuht12-oss/marketing-skills4,5622026年10月13日 更新

Reviews all your Google Ads extensions — sitelinks, callouts, structured snippets, call extensions, image extensions, price extensions — across every campaign. Flags what's missing, what's underperforming, what's outdated, and writes replacements based on your best performing ads and landing pages. Platform: Google.

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

irinabuht12-oss/marketing-skills4,5622026年10月13日 更新

tests-run

無料

Execute Unity tests (`EditMode` or `PlayMode`) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.

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

IvanMurzak/Unity-MCP4,4582026年10月13日 更新

List every scene currently opened in the Unity Editor as a shallow snapshot (name, path, build flags). Use 'scene-get-data' for the deep view of a specific scene.

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

IvanMurzak/Unity-MCP4,4582026年10月13日 更新

Regenerate every `SKILL.md` from the project's currently-registered MCP tools into the configured skills folder (or a project-relative override path). Writes the YAML `description:` from `[AiSkillDescription]` and the body from `[AiSkillBody]`.

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

IvanMurzak/Unity-MCP4,4582026年10月13日 更新

Provides an initial setup for AI Skills, `unity-mcp-cli` command line tool installation and everything else that is helpful to set up at the start of the project. Essential packages, and basic configurations.

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

IvanMurzak/Unity-MCP4,4582026年10月13日 更新

Find C# methods across every loaded assembly by name / type / parameters — including private methods. Returns serialized `MethodData` entries usable as schemas for 'reflection-method-call'.

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

IvanMurzak/Unity-MCP4,4582026年10月13日 更新

Get asset data from the asset file in the Unity project — every serializable field and property. Supports token-saving path-scoped reads via `paths` or `viewQuery`. Use 'assets-find' to find the asset first.

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

IvanMurzak/Unity-MCP4,4582026年10月13日 更新

Create a new folder under a parent folder inside 'Assets/'. The parent path must start with 'Assets/' and every intermediate folder in it must already exist. Refreshes the AssetDatabase at the end and returns the GUID(s) of the created folder(s).

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

IvanMurzak/Unity-MCP4,4582026年10月13日 更新

List the fully-qualified C# type names of every concrete `UnityEngine.Component` subclass available in the project. Paginated (default 5/page, max 500). Use this to find a valid `componentName` for 'gameobject-component-add'.

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

IvanMurzak/Unity-MCP4,4582026年10月13日 更新

verify-bb

無料

Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected recipes and platform prerequisites.

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

get-bb/bb4,3052026年10月14日 更新

modlens

無料

Plug-in vision for text-only models. Hard rule: when a file path or URL with an image extension (.png, .jpg, .jpeg, .webp, .gif, .heic, .heif) appears anywhere in the conversation (typed by the user, injected as a `[Image: source: <path>]` line, or inside a tag) and you cannot see that image's content, run this skill on it before any other approach: no self-built OCR, no PIL, no tesseract. Also triggers on pasted-image placeholders such as `[Image #1]` and `[Unsupported Image]`. If you can actually see the image, do not use this skill. When unsure, run `modlens guard` before the first read of a session: a deny verdict means the active model has native vision and must read the image itself. Runs the modlens CLI to convert the image into structured JSON evidence: every word transcribed, layout regions, semantics, visual clues. Also use when the user asks how to install, configure, or switch modlens providers (Gemini API key, OpenAI-compatible endpoints, Claude API or Claude Code CLI).

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

liustack/modlens4,2582026年10月4日 更新

Starter: one-screen provider health summary — availability, auth method, version drift, and cost posture for every seatable provider

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

nyldn/claude-octopus4,2362026年10月14日 更新

Principles for writing skills that behave the same way every run — use when adding, editing, or reviewing a skill in this plugin

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

nyldn/claude-octopus4,2362026年10月14日 更新

Read every ADR markdown file in the project's docs/adr/ folder so you have full context on past decisions. Use only when the user explicitly calls it.

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

davidondrej/skills4,1402026年10月14日 更新

docs-sync

無料

Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-writer + python-architect + editorial-owner + growth-hacker loop to produce a patch-ready advisory. Does NOT review code quality, security, or test coverage. Does NOT auto-merge or auto-push doc edits.

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

microsoft/apm4,0102026年10月12日 更新

Use this skill to write the PR description (PR body) for any pull request opened against microsoft/apm. Produces one self-sufficient GitHub-Flavored Markdown artifact: TL;DR, Problem (WHY), Approach (WHAT), Implementation (HOW), 1-3 validated mermaid diagrams, explicit trade-offs, validation evidence, and a How-to-test section -- with every WHY-claim backed by a verbatim quote from PROSE or Agent Skills. Activate when the user asks to "write a PR description", "draft a PR body", "open a PR", "fill in the PR template", or any equivalent.

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

microsoft/apm4,0102026年10月12日 更新

Queue microsoft/apm pull requests labelled `panel-review` (or an explicit named list) and fan them out through an isolated pool (default 2) of autopilot-pr-review-worker sessions. Advisory only. Never implements. Never composes autopilot-pr-merge-worker. Never review every open PR. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow. Does not triage issues or open greenfield PRs.

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

microsoft/apm4,0102026年10月12日 更新

Drive ONE already selected open pull request in microsoft/apm to mergeable. Classifies copilot-pull-request-reviewer[bot] inline review, runs autopilot-pr-review-worker, folds (by default) every recommendation inside the PR's stated scope, pushes to the head branch or a superseding PR that preserves authorship via commit trailers, watches CI to green (`agent-merge` when that skill or `<agent_merge_state>` is present; otherwise `gh pr checks --watch`), and iterates under fixed caps until ready-to-merge, advisory-with-deferred, superseded, or blocked. Plan before any fold, push, or reviewer request. Never spawned by autopilot-pr-review-scheduler. That scheduler is advisory only. Invoke this skill by name when the caller asked to drive a PR to merge.

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

microsoft/apm4,0102026年10月12日 更新

Write or refine Chinese technical notes and articles in a concise, evidence-led voice. Use for substantive drafting or rewriting, not every Chinese reply.

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

huangruiteng/CS-Notes4,0062026年10月15日 更新

Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before command, every technical term defined at first use, no AI slop. Default mode is Plain. Strict mode applies full STE vocabulary compliance when the user names STE, ASD-STE100, or compliance. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, and explanations for readers outside the field. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "plain English", "layman's terms", "explain it simply", "no jargon", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. The same rules govern the reply: answer first, prose only.

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

AminBlg/SimpleEnglish3,9232026年10月6日 更新