4,061 件 ・ 関連度順
概要と使いどころ
Validate a bug bounty finding before writing a report — the 7-Question Gate, 4 pre-submission gates, always-rejected list, conditional chain table, CVSS 3.1 quick reference, and severity decision guide. Use BEFORE writing any report to avoid N/A and low quality submissions.
日本語の概要は準備中です。原文の説明を表示しています。
Run a Programme phase gate validator (requirements / design / test / code) against docs/specs/<feature-id>/. Block on missing artefact or broken cross-phase reference.
日本語の概要は準備中です。原文の説明を表示しています。
Send, read, and respond to Telegram messages as Claudicle via the @claudicle_bot Bot API. Use this skill when sending Telegram messages (text, Markdown, inline keyboards), building approval gates with tappable buttons, checking the shared inbox for unhandled Telegram messages, answering callback queries, managing Telegram memory context, or checking bot and listener status. Five purpose-built scripts (send, check, status, callback, memory) wrap the python-telegram-bot v22 polling adapter at ~/.claudicle/adapters/telegram/ with REST-based senders (no asyncio). Pairs with /telegram-respond for the cognitive pipeline and with mazkir-callback-watcher.py for the Mazkir approval gate.
日本語の概要は準備中です。原文の説明を表示しています。
Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, validates, packages, tests, and optimizes deployment-ready Skill files (SKILL.md + references/ + scripts/ + agents/) from design specifications. Three pre-build gates + 9-dimension quality gate (with D9a/b/c empirical evidence tiers) + behavioral iteration loop + automated description optimizer + blind version comparator. Use for building, reviewing, revising, testing, or optimizing Skills. Trigger on: "build this Skill," "review this Skill," "test my Skill," "optimize the description," "compare these Skill versions," "should this be a hook instead," "build a template first." Also: "my Skill doesn't activate," "my description truncates," "my SKILL.md is too long," "my Skill is overtriggering." Do NOT use when designing Skill methodology — that's design work, not packaging. Do NOT use for prompt compilation, project auditing, or prompt scoring (use rootnode-prompt-compilation, rootnode-project-audit, or rootnode-prompt-validation if available).
日本語の概要は準備中です。原文の説明を表示しています。
Selects the active profile from triggering context. Evaluates a rule set against inputs (current time, calendar state, geofence, manual command, custom signals) and returns the profile name that consuming Skills (handoff-trigger-check, critic-gate, future Skills) should apply. Configuration-driven; rule set lives in a router config file conforming to the included schema. Deterministic precedence — manual override beats calendar beats time-window beats default. Required default profile guarantees a routing decision always exists. Use when an orchestrator needs to pick a profile automatically rather than having the caller specify one, when wiring calendar/time/Telegram triggers to gate behavior, or when a Skill's behavior should change with availability mode. Trigger on: "what profile should I use," "route to a profile," "which mode am I in," "auto-select profile," "active mode," "current profile." Do NOT use to evaluate work readiness or review proposed changes. Always returns a profile name.
日本語の概要は準備中です。原文の説明を表示しています。
Probe the runtime state of a named feature flag in a CLI binary. Covers the four-pronged evidence protocol (binary strings, live invocation, on-disk state, platform cache), the four-state classification (LIVE / DARK / INDETERMINATE / UNKNOWN), gate-vs-event disambiguation, conjunction-gate handling, and skill-substitution scenarios where a flag appears DARK but the capability is delivered by other means. Use when verifying whether a documented or inferred capability has rolled out, when auditing dark-launched features, or when a prior probe's conclusions need refreshing against a new binary version.
日本語の概要は準備中です。原文の説明を表示しています。
Redact reverse-engineering findings for public disclosure while preserving methodology, generalizable patterns, and teaching value. Covers the private-vs-public repo split, deny-list pattern maintenance, orphan-commit publish pattern that prevents `git log` leaks, category-based redaction calibration (methodology/pattern/version-finding/internal), and the `check-redaction.sh`-style CI gate that blocks merges when a deny-listed pattern appears. Use when publishing findings about a CLI harness you don't own, when preparing upstream proposals to an unrelated project, or when archiving a private research repo for public reference.
日本語の概要は準備中です。原文の説明を表示しています。
Guide a person through a Coordinate Remote Viewing (CRV) session following the Stargate/SRI protocol. AI acts as the monitor/tasker role, managing protocol progression, catching Analytical Overlay (AOL), and redirecting the viewer through stages I-VI. Use when a person wants to practice CRV and needs a monitor to manage the session protocol, when training a viewer through the staged CRV process, facilitating a structured intuitive perception exercise, or developing non-local awareness skills that complement healing work.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.
日本語の概要は準備中です。原文の説明を表示しています。
Apply GitHub repository security protections tier by tier — rulesets, read-only Actions token, secret scanning + push protection, Dependabot, and (gated) required status checks / required PR with a GitHub App bypass for a CI auto-commit bot. Mutating and confirmation-gated: always assess first, apply the no-regret baseline, then decide required checks separately. Use when hardening a public user-owned repo after an audit, when a repo has no branch protection, when adding required checks without breaking a bot that pushes to the default branch, or when provisioning a GitHub App bypass actor for trusted automation.
日本語の概要は準備中です。原文の説明を表示しています。
Implement policy-as-code enforcement using OPA Gatekeeper or Kyverno to validate and mutate Kubernetes resources according to organizational policies. Covers constraint templates, admission control, audit mode, reporting violations, and integrating with CI/CD pipelines for shift-left policy validation. Use when enforcing resource configuration standards, preventing security misconfigurations such as privileged containers, ensuring compliance before deployment, standardizing naming conventions, or auditing existing cluster resources against policies.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate complex development with AUTOMATIC parallel subagent execution, continuous dispatch scheduling, dependency analysis, file conflict detection, and IOSM quality gates. Analyzes task dependencies, builds critical path, launches parallel background workers with lock management, monitors progress, auto-spawns from discoveries. Use for multi-file features, parallel implementation streams, automated task decomposition, brownfield refactoring, or when user mentions "parallel agents", "orchestrate", "swarm", "continuous dispatch", "automatic scheduling", "PRD", "quality gates", "decompose work", "Mixed/brownfield".
日本語の概要は準備中です。原文の説明を表示しています。
Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.
日本語の概要は準備中です。原文の説明を表示しています。
Run a strict multi-iteration Reflex Loop with phases (PLAN, PRODUCE||PREPARE, EVALUATE, CRITIQUE, REFINE) to improve an artifact until quality gates pass or iteration limits are reached. Use when user asks for iterative refinement, quality-gated generation, or "generate -> critique -> refine" loops.
日本語の概要は準備中です。原文の説明を表示しています。
Run a strict multi-iteration Reflex Loop with phases (PLAN, PRODUCE||PREPARE, EVALUATE, CRITIQUE, REFINE) to improve an artifact until quality gates pass or iteration limits are reached. Use when user asks for iterative refinement, quality-gated generation, or "generate -> critique -> refine" loops.
日本語の概要は準備中です。原文の説明を表示しています。
Find authoritative guidance for installing, configuring, operating, securing, and troubleshooting OpenClaw, including channels, model providers, Gateway operations, tools, plugins, automation, nodes, multi-agent routing, and CLI errors. Use for any question or maintenance task involving an OpenClaw installation, `openclaw` CLI command, Gateway daemon, configuration key, or integration.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate an evidence-gated electronic product and PCBA workflow from an idea, circuit description, schematic, netlist, PCB, BOM, or fabrication package through a reviewed order. Use for end-to-end requests, multi-stage hardware projects, workflow recovery, gate tracking, change invalidation, or deciding which specialist skill is required next.
日本語の概要は準備中です。原文の説明を表示しています。
Decomposition playbook and anti-temptation rules for an orchestrator agent that routes work through the Surogates subagent task layer. Pair this skill with an AgentDef whose tool filter strips the implementation tools (terminal, file, web, code) — that's how 'don't do the work yourself' is enforced structurally, not just behaviorally.
日本語の概要は準備中です。原文の説明を表示しています。
Hard-gated ideation for an Arbor research run. Load at the START of every IDEATE round, before drafting any hypothesis. Enforces the PI mindset (mechanism over knob), the four-question first-principles probe, the kill-filter, and the four-line hypothesis format. Ported from Arbor's idea_drafting + first_principles_probe.
日本語の概要は準備中です。原文の説明を表示しています。
DECIDE-phase doctrine for an Arbor research run: when to merge, prune, combine, or finalize; how the held-out merge gate works; and the rule that the final report uses TEST scores. Load before deciding what to do with completed experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Pitfalls, examples, and edge cases for workers executing a Surogates subagent task. Loaded automatically when the dispatcher spawns a session bound to a Task (Session.task_id is set).
日本語の概要は準備中です。原文の説明を表示しています。
Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "interact", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".
日本語の概要は準備中です。原文の説明を表示しています。
Teaches you how to delegate tasks to Cowork so clearly that you get exactly what you asked for — every time. Use when learning how to give better instructions, for improving your delegation technique, during early Cowork adoption when results feel off, when writing clearer task descriptions, or when the user says "how do I ask cowork to do things", "delegation tips", "better instructions", "cowork isn't doing what I want", "help me delegate", "my results are bad", "how do I give better prompts", "cowork keeps getting it wrong", "I don't know how to use this", or "how do I get good results".
日本語の概要は準備中です。原文の説明を表示しています。