1,813 件 ・ 関連度順
概要と使いどころ
Use when working with Bitbucket Pr Reviews — bitbucket pull request review management including default reviewers, merge checks, branch permissions, and build status integration. Use when configuring or automating Bitbucket PR review workflows across repositories and workspaces.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Bitbucket Deep — bitbucket deep platform management covering repository inventory, Pipelines CI/CD monitoring, pull request analysis, branch permission auditing, deployment environment tracking, and workspace member management. Use when auditing repository configurations, investigating pipeline failures, reviewing branch restrictions, or managing workspace access.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Iam — aWS IAM deep analysis for policy evaluation, role trust relationship review, access advisor data, credential reports, permission boundary inspection, and identity-based vs resource-based policy analysis. Covers IAM users, roles, groups, policies, SCPs, and cross-account access patterns. Read this skill before any IAM operations — it enforces discovery-first patterns and strict read-only safety rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Baserow — baserow open-source database platform management covering workspace organization, database and table inventory, field configuration analysis, view management, webhook monitoring, and user access auditing. Use when reviewing database structures, investigating API integration issues, monitoring webhook deliveries, or auditing workspace permissions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Azure Lighthouse — azure Lighthouse delegated resource management. Covers delegation assignments, managed service offers, customer tenant access, cross-tenant resource visibility, role assignments, and delegation auditing. Use when managing multi-tenant Azure environments, reviewing delegated access, auditing cross-tenant permissions, or configuring managed service registrations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Appsmith — appsmith low-code platform management covering application inventory, workspace organization, datasource health, page and widget analysis, and user access auditing. Use when reviewing internal tool configurations, investigating datasource connectivity, monitoring application deployments, or auditing workspace permissions.
日本語の概要は準備中です。原文の説明を表示しています。
Port-scan, deps, permissions, network, password hygiene.
日本語の概要は準備中です。原文の説明を表示しています。
' - **Content:** The user provided a list of daily paper submissions with titles, authors, and some metadata. I need to extract the single most valuab
日本語の概要は準備中です。原文の説明を表示しています。
AI agent system prompts cannot serve as the sole enforcement layer — guardrails must be implemented at the API gateway and token-permission level, not
日本語の概要は準備中です。原文の説明を表示しています。
How to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for experimental characterization. Also trigger when code imports `adaptyv`, `adaptyv_sdk`, or `FoundryClient`, or references `foundry-api-public.adaptyvbio.com`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).
日本語の概要は準備中です。原文の説明を表示しています。
Systematic strategic planning framework for philosophy and interdisciplinary academic papers targeting preprint platforms (PhilArchive, arXiv, PhilSci-Archive). Use when users want to: (1) plan a paper on a specific topic, (2) identify research gaps and assess originality, (3) develop optimized paper outlines, (4) prepare for preprint submission, or (5) understand platform requirements and writing standards. Triggered by phrases like 'plan a paper on,' 'help me design a paper about,' 'identify research gaps in,' 'is this idea original,' or when users need structured research planning. The skill guides through three phases: Platform Analysis (identifying target venue and studying sample papers), Theoretical Framework (AI-driven literature search and gap identification), and Outline Optimization (structured design with reviewer-perspective self-assessment). Each phase includes quality evaluation standards and validation checkpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Use OpenAI, Anthropic, Google Gemini, or OpenRouter models from Netlify Functions or Edge Functions without managing provider API keys or accounts — the gateway injects credentials automatically. Reach for this when you add an AI chatbot or completion endpoint, generate images or text with Gemini/GPT/Claude, summarize form submissions with AI, build an LLM-backed API route, stream a long AI generation, or wire up any server-side AI provider call on Netlify. Covers provider SDK setup, injected env vars, model availability, rate limits, credit costs, streaming for long generations, and local dev with netlify dev or the Vite plugin.
日本語の概要は準備中です。原文の説明を表示しています。
Store and retrieve unstructured objects, file uploads, and cache-like state on Netlify using the @netlify/blobs key/value API from Functions, Edge Functions, and Build Plugins. Use when a task involves saving user file or image uploads, persisting form or contact-form submissions, storing generated output from Background Functions (sitemaps/processed media/bulk-email results), building read-only asset stores, adding client-side blob expiration, or wiring file-based blob uploads at deploy time. Not for per-user, transactional, or relational data (counters/balances/sessions) — reach for Netlify DB there instead.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure a usable SageMaker execution role exists before deploying or training. Use this skill whenever about to create a SageMaker endpoint, model, training job, or any resource that requires an execution role. Use it especially when the user has not provided a role ARN explicitly, when scripts are about to call `iam:CreateRole`, or when an AccessDenied error mentions an IAM action. Never blindly call `iam:CreateRole` — always check for existing roles first. This skill prevents the most common SageMaker deployment failure: trying to create IAM resources from an SSO principal that has no IAM write permissions.
日本語の概要は準備中です。原文の説明を表示しています。
Carbon Footprint Specialist IA — Expert en empreinte carbone (GHG Protocol, Scope 1-3, carbon offsets, reporting)
日本語の概要は準備中です。原文の説明を表示しています。
Scan agent skills for security issues before adoption. Detects prompt injection, malicious code, excessive permissions, secret exposure, and supply chain risks.
日本語の概要は準備中です。原文の説明を表示しています。
Helps an AI assistant work with the Miraheze wiki farm — writing wiki requests that get approved, navigating ManageWiki, doing common how-to tasks (templates, skins, permissions, custom domains, backups), writing regex for MediaWiki search-and-replace, AND writing actual article and page content for Miraheze-hosted wikis. Miraheze does NOT ban generative AI; AI-written content is permitted (subject to per-wiki rules). MADE BY SQERSTERS
日本語の概要は準備中です。原文の説明を表示しています。
Check the machine and the current project, and print suggested permissions.allow entries without writing any settings. Generated from plugin-commands.json; invoke as $bdb-aos:doctor.
日本語の概要は準備中です。原文の説明を表示しています。
How to use windows-computer-use-mcp effectively — tool selection, focus rules, safety, and mission design.
日本語の概要は準備中です。原文の説明を表示しています。
Change the agent harness itself (AOS, AO or CBS hooks, gates, memory, permissions, delegation, plugins, bootstrap) the safe way: look up the matching harness pattern, design against its gotchas, build with /startcycle and a live trail, check every harness, open a PR after GO. Use for "change a hook", "fix the go-gate", "harness work", "plugin change".
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission. Use when preparing an app for App Store review, after receiving a rejection from Apple, or when auditing metadata, subscriptions, privacy manifests, entitlements, or design compliance. Integrates with the asc CLI for metadata inspection.
日本語の概要は準備中です。原文の説明を表示しています。
Resize and validate App Store screenshots with current asc screenshot-size data and macOS sips. Use when preparing or fixing screenshots for App Store Connect submission.
日本語の概要は準備中です。原文の説明を表示しています。