2,508 件 ・ 関連度順
概要と使いどころ
Build RAG (Retrieval-Augmented Generation) agents with Google ADK and Vertex AI RAG Engine. Use when implementing document Q&A, knowledge base search, or citation-backed responses. Covers VertexAiRagRetrieval tool, corpus setup, and citation formatting.
日本語の概要は準備中です。原文の説明を表示しています。
Run the oncall handoff for a rotation window — the whole handoff, not just a document: build the summary (what the incoming oncall needs first, what's still open, incidents with impact numbers, alert and page counts, hygiene suggestions, every number traceable to a source), post it for the outgoing oncall to correct, walk the incoming oncall through the open items in the thread, update the list as they respond, and note when they acknowledge. Runs mainly in the team's standing oncall / monitoring channel, normally as a scheduled routine firing at rotation change so the report is waiting when the shift turns over; can also be run by hand and works from an incident channel. Use when a handoff routine fires, or on "handoff", "hand over", "oncall summary", "weekly oncall report", "what happened this shift / this week". Re-running for the same window updates the report rather than duplicating it. Unattended runs carry a run-summary block and at least one chart.
日本語の概要は準備中です。原文の説明を表示しています。
Query and manage PagerDuty — find out who's on call, list and manage incidents, read escalation policies and schedules, trace who got paged and why, acknowledge/resolve/snooze/escalate incidents, and create or update services. Use this whenever the user mentions PagerDuty, on-call, paging, escalation, an incident ID like `PXXXXXX` or `Q...`, asks "who's on call", "page the on-call", "ack this incident", "why wasn't I paged", or pastes a pagerduty.com URL — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Search the company's enterprise knowledge index. Use this FIRST when starting any task that touches company-specific context - projects, people, policies, internal docs, prior decisions - before searching individual sources like Drive, Slack, or Jira directly. Also use it when the user asks "do we have a doc about X", "what's our policy on Y", or references internal initiatives by name. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever the user wants to find, shortlist, vet, or enrich US cybersecurity firms — pen-testing/red team, security audits, vCISO, SOC 2 readiness, incident response, managed SOC, IAM, cloud security, and AppSec. Triggers on "find me a pen-testing firm for our SOC 2 audit", "shortlist three vCISO services for our healthcare-tech startup", "we need an incident response retainer", or "pull contact info for these 8 security firm domains", even when described indirectly (we got breached, prepare us for the compliance audit, get us SOC 2 ready). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Skip in-house security hires, "how do I patch CVE-X" or "configure firewall Y" DIY questions, security-product reviews (CrowdStrike vs SentinelOne, etc.), generic security knowledge questions, consumer/personal security advice, non-US firms, individual freelancers and bug-bounty hunters.
日本語の概要は準備中です。原文の説明を表示しています。
Create or revise repo-local skills connected by actionable routing statements from AGENTS.md through broad and increasingly specialized skills. Use when documenting AuthCrunch engineering knowledge, adding or routing a skill, reorganizing the skill hierarchy, or auditing that every skill is reachable and useful to contributors.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Feishu channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Feishu channel.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare to contribute to an open source repo. Reads all contribution docs, checks eligibility, assesses the user's knowledge gaps, and fills them before coding starts. Use after finding an issue with oss-find-issue, or when starting work on any OSS repo. Not for installing dependencies or getting the build and tests running. Use oss-setup-dev-env for that.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating new skills in Kai's personal AI infrastructure. Use when user wants to create, update, or structure a new skill that extends capabilities with specialized knowledge, workflows, or tool integrations. Follows both Anthropic skill standards and PAI-specific patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Git-as-knowledge-graph workflow for traceability. Use when planning work, brainstorming designs, creating/managing issues and PRs, tracking architectural decisions, or resuming prior sessions. Slash command /shiplog.
日本語の概要は準備中です。原文の説明を表示しています。
通用知识沉淀能力 - 提供从项目交付过程中提炼可复用经验、教训和模式的标准化方法论，包括信息收集、精简提炼、结构化输出。不绑定任何特定工作流或存储方式。当用户说"帮我做知识沉淀"、"总结一下这次需求的经验"、"记录一下踩坑"、"沉淀一下这次的技术决策"、"做个复盘"时使用本技能。
日本語の概要は準備中です。原文の説明を表示しています。
通用知识沉淀能力。用于从 devflow 或其他交付过程的需求、设计、实现、审查、测试产物中提炼可复用经验、技术决策、踩坑记录和流程改进。
日本語の概要は準備中です。原文の説明を表示しています。
Odoo 17 development reference for Python models and ORM (search, domain, read_group, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work involves Odoo 17 or custom addons, including traceback diagnosis, addons, manifests, XML errors, HTTP controllers, business rules, feature work, refactoring, or reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo engineering workflows for addon development, codebase exploration, debugging, architecture/refactor review, manifest/docs sync, and routing to migration work. Use when the user mentions Odoo, addons, modules, manifests, models, XML views, security CSVs, record rules, Odoo shell, OWL/QWeb/assets, or when an Odoo codebase is detected.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo website and portal engineering guidance for QWeb templates, public and portal controllers, website models, frontend assets, and route integration. Use when working on Odoo website pages, portal flows, public forms, QWeb, website templates, portal access, or frontend behavior outside a pure OWL component.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo browser-facing test guidance for HTTP controllers, website and portal flows, QWeb templates, assets, OWL integration, browser tours, and JavaScript behavior. Use when testing or debugging public pages, portal access, forms, controllers, frontend assets, or end-to-end Odoo web behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo-specific grilling session that stress-tests addon plans, migrations, model/view/security designs, OWL frontend changes, and verification strategy. Use when the user wants to be grilled on an Odoo plan/design, asks to stress-test an addon architecture, or mentions grill me in an Odoo context.
日本語の概要は準備中です。原文の説明を表示しています。
Review Odoo addon code for correctness, security, performance, migrations, tests, and official Odoo coding guidelines. Use when reviewing Odoo modules, diffs, pull requests, or changed files involving models, fields, XML views, data, controllers, reports, OWL/assets, manifests, access rules, record rules, or OCA migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo 18 development reference for Python models and ORM (search, domain, read_group, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work involves Odoo 18 or custom addons, including traceback diagnosis, addons, manifests, XML errors, HTTP controllers, business rules, feature work, refactoring, or reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Search markdown knowledge bases, notes, and documentation using QMD. Use when users ask to search notes, find documents, or look up information.
日本語の概要は準備中です。原文の説明を表示しています。
Unified code intelligence — Skeleton Index (zero-dep, <4s) + AST knowledge graph (CodeGraph) + architecture diagrams (Mermaid) + smart context builder. Pre-indexes code structure so AI agents understand any codebase instantly. 95% token compression for onboarding. 30% fewer tokens for deep analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Emoji reactions and thinking indicators for XMTP agents. Use when adding reactions to messages or showing processing state with thinking emoji. Triggers on emoji reactions, thinking indicator, or message acknowledgment.
日本語の概要は準備中です。原文の説明を表示しています。
Self-knowledge for stella, the self-hosted AI assistant. Use when users ask about configuration, setup, onboarding, providers, models, agents, channels, webhooks, memory, schedules, workflows, goals, workers, skills, plugins, session compaction, notifications, self-update, multi-user behavior, or how stella works. Also use for changing models, setting up channels or webhooks, configuring providers, updating stella, onboarding, switching agents, reporting bugs, and goal status or acceptance.
日本語の概要は準備中です。原文の説明を表示しています。
Use GBrain to give OpenClaw or Hermes-style agents a local knowledge brain with markdown ingestion, entity links, hybrid search, scheduled consolidation, and MCP access.
日本語の概要は準備中です。原文の説明を表示しています。