4,945 件 ・ 関連度順
概要と使いどころ
Use this skill when the user asks about CMV maintenance program requirements under 49 CFR 396.3 — what records must be kept, retention periods (12-18 months on vehicle file + 1 year after disposal), what counts as systematic inspection/repair/maintenance, preventive maintenance scheduling, brake adjustment records, and what auditors look for in vehicle files. Cite 49 CFR 396.3 + 396.21.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when documenting supervisor reasonable-suspicion training for Part 382 compliance. Covers what to log, what to retain, and what training providers to use.
日本語の概要は準備中です。原文の説明を表示しています。
Extract exactly what the person typed in a Claude Code session (script, no agent context spent), have a fresh agent write a faithful structured summary under it, and optionally have an adversarial agent judge whether the working agent is still on track. Use at a checkpoint, before a handoff, after a compaction, when a long session may have drifted from what the owner asked, or when told to 'summarize what I said' or 'check we're on track'.
日本語の概要は準備中です。原文の説明を表示しています。
Finds what changed in Claude — docs, release notes, changelogs, GitHub and community posts on Claude Code, claude.ai, Cowork, the API and models — and turns each change into adopt rows for your setup, plus a fit card for a new model or feature and a monthly bench of your skills against public skill and plugin repos (build, adopt or skip). Trigger on what changed since a date or version, a weekly sweep, features worth adopting, a feature that broke unannounced, a stale model table, what a new model or feature is good for, or how your skills compare with popular or little-known skill and plugin repos; or say scoutwright (sweep, since, watch, adopt, fit, bench, sources, refresh). Outside research is researchscribe's; applying a row, skillwright's; config, rigwright's; schedules, agentwright's; tier picks, promptwright's.
日本語の概要は準備中です。原文の説明を表示しています。
After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.
日本語の概要は準備中です。原文の説明を表示しています。
Start here. Introduces what NemoClaw is, what agent skills are available, and which skill to use for a given task. Use when discovering NemoClaw capabilities, choosing the right skill, or orienting in the project. Trigger keywords - skills, capabilities, what can I do, help, guide, index, overview, start here.
日本語の概要は準備中です。原文の説明を表示しています。
Guide a startup to set a single quantified traction goal and define the critical path of milestones to reach it. Use whenever a founder needs to prioritize activities, set growth goals, define milestones, decide what NOT to work on, plan quarterly/yearly execution, cascade goals to teams, escape the 'too many things to do' trap, or apply a binary on-path/off-path filter to proposed work. Activates on phrases like 'traction goal', 'critical path', 'what should we focus on', 'too many priorities', 'prioritization', 'milestones', 'quarterly planning', 'yearly goals', 'OKRs', 'where should I spend my time', 'what NOT to do', 'company planning', 'goal setting', 'DuckDuckGo', 'roadmap'.
日本語の概要は準備中です。原文の説明を表示しています。
Track what a competitor actually shipped — "watch this competitor", "track what they ship", "what changed at". Compares against the last snapshot and reports only real moves: launches, pricing changes, positioning shifts.
日本語の概要は準備中です。原文の説明を表示しています。
Periodic dependency update run. Reads what the package manager says is outdated, upgrades what is safe, applies the code changes the new versions need, verifies, and opens one reviewable PR. Supports a read-only dry run that reports what it would do. Use when the user says "dependency update", "/dependency-update", "update deps", "dry run the dep update", or when a scheduled cloud routine fires.
日本語の概要は準備中です。原文の説明を表示しています。
Status overview of an .aiwork/ task folder — what is done, what is awaiting the human, what is blocked, and the one next action. Auto-detects the most recent task folder when no argument is given.
日本語の概要は準備中です。原文の説明を表示しています。
Use FIRST when someone asks for a new feature or a change to an existing one — before any schema, code or test. Works out what is actually being asked for, whether to build it or integrate a third party (Trustpilot, Stripe, Calendly and the like), where the data lives, who may do what, and what happens when the vendor is down. Produces a decision, then hands to feature-schema.
日本語の概要は準備中です。原文の説明を表示しています。
Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments). Routes to all other skills based on current hunting phase. Also use when asking 'what should I do next' or 'where am I in the process.'
日本語の概要は準備中です。原文の説明を表示しています。
Search and browse the x402 bazaar marketplace for paid API services. Use when you or the user want to find available services, see what's available, discover APIs, or need an external service to accomplish a task. Also use as a fallback when no other skill clearly matches — search the bazaar to see if a paid service exists. Covers "what can I do?", "find me an API for...", "what services are available?", "search for...", "browse the bazaar".
日本語の概要は準備中です。原文の説明を表示しています。
X Intelligence CLI — search, analyze, and engage on X/Twitter from the terminal. Use when: (1) user says "x research", "search x for", "search twitter for", "what are people saying about", "what's twitter saying", "check x for", "x search", "search x", "find tweets about", "monitor x for", "track followers", (2) user is working on something where recent X discourse would provide useful context (new library releases, API changes, product launches, cultural events, industry drama), (3) user wants to find what devs/experts/community thinks about a topic, (4) user needs real-time monitoring ("watch"), (5) user wants AI-powered analysis ("analyze", "sentiment", "report"). Also supports: bookmarks, likes, following (read/write), trending topics, Grok AI analysis, and cost tracking. Export as JSON, JSONL (pipeable), CSV, or Markdown. Non-goals: Not for posting tweets, not for DMs, not for enterprise features. Requires OAuth for user-context operations (bookmarks, likes, following, diff).
日本語の概要は準備中です。原文の説明を表示しています。
Show what this NanoClaw instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs /capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
OpenClawのリリース情報を確認し、Discord向けの告知文を作成します。版ごとの更新手順や利用者に試してほしい点を整理し、投稿にも対応します。
OpenClawのQAシナリオを模擬環境や実サービスで実行し、失敗原因の修正、結果レポートの確認、複数モデルの応答スタイル比較まで支援するスキル。
会話で話し合った内容とコードベースの理解から仕様書を作り、プロジェクトのIssue管理先に公開します。課題、利用者の要望、実装・テスト方針、対象外を整理します。
一度の対話では収まらない大きな企画や変更を、決めるべき問いと依存関係に整理します。課題管理ツールに判断の記録を残し、実行に移るまでの道筋を明らかにするスキル。
既存のテストと不足箇所を棚卸しし、要件・業務ルール・不具合を識別番号と実行結果に結び付け、何が検証済みかをテスト台帳で追跡します。
既存コードの一部を監査し、設計判断の記録・実装慣行・不足機能・技術選定の四つの観点で課題を整理して、計画からテスト、修正、再監査まで進めます。
作業環境の設定や接続済みツールを読み取り、今使える機能と不足を整理するスキル。Claude Codeなどで次に整えるECCのスキルや連携を提案します。
公開前や変更の取り込み後に、アプリの認証・データ・決済・運用を根拠付きで点検します。公開を妨げる問題と優先して直す項目を、本番への準備状況としてまとめるスキル。
複雑な作業や失敗から、根本原因、次回の行動、問題を見分ける兆候を抽出し、再利用できる学習記録にまとめます。同じ原因の既存記録との重複も整理します。