「auth」の検索結果

Redpanda's Agentic Data Plane: governance infrastructure for building, running, and governing AI agents and MCP servers, plus a proxying AI Gateway for LLM providers, operated via `rpk ai` and the ADP API. Use when creating or managing AI agents (managed or self-managed) via `rpk ai agent` or `AgentRegistryService`; configuring MCP servers (remote or managed catalog, code mode, auth); setting up LLM providers or querying models via `rpk ai llm`/`rpk ai model` or the AI Gateway proxy; or configuring budgets, guardrails, or Cedar access-control policies through the governance APIs. Also covers reading agent transcripts and spending insights, and wiring OAuth clients or providers to the aigw Authorization Server. For the separate rpk cloud mcp control-plane MCP server, see `/redpanda:rpk-cloud`.

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

Use for authorized security assessment of REST, GraphQL, WebSocket, or SOAP APIs, including discovery, authentication, authorization, rate-limit, and CI/CD testing.

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

Clerk is a hosted authentication and user-management service with drop-in UI components, social login, email/password, organizations, RBAC and webhooks. Use when adding sign-in to Next.js, React, or Express apps, protecting routes with clerkMiddleware, setting up multi-tenant organizations and roles, or syncing Clerk users to your own database.

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

You are an expert in Composio, the platform that gives AI agents access to 250+ external tools and APIs with managed authentication. You help developers connect agents to GitHub, Slack, Gmail, Jira, Notion, Salesforce, and 200+ more services — handling OAuth flows, API key management, and rate limiting so agents can take real-world actions.

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

Build backends with Appwrite — open-source Backend-as-a-Service. Use when a user asks to set up user authentication, manage a database without writing backend code, handle file storage and uploads, add realtime subscriptions, set up cloud functions, build a mobile or web app backend, replace Firebase with an open-source alternative, or self-host a BaaS platform. Covers auth, databases, storage, functions, realtime, and SDK integration for web, mobile, and server-side.

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

The craft of weaving story into interactive systems where the player is both audience and author. This skill covers the unique challenges of game narrative: branching structures that respect player agency, environmental storytelling that rewards exploration, dialogue systems that feel alive, and the delicate balance between authored experience and emergent narrative. Unlike linear media, games don't tell stories TO players - they create the conditions for stories to emerge WITH players. The narrative designer's job is to build the scaffolding that supports infinite player-authored moments while maintaining coherent themes and emotional arcs. This skill synthesizes lessons from Disco Elysium's internal monologue as gameplay, Hades' death-as-narrative-engine, interactive fiction's branching mastery (Inkle, Twine), and procedural narrative pioneers like Dwarf Fortress. It addresses ludonarrative harmony, bark systems, cinematics that respect agency, and the "and therefore" test that separates plot from story. Use when "narrative design, game story, game writing, dialogue system, branching narrative, player choice, environmental storytelling, bark system, quest design, lore delivery, ludonarrative, interactive fiction, inkle, twine, dialogue tree, player agency, cinematic design, voice direction, localization, procedural narrative, narrative, game-writing, dialogue, branching, player-agency, environmental-storytelling, quest-design, voice-acting, localization, interactive-fiction, procedural-narrative, ludonarrative" mentioned.

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

API Security Best Practices workflow skill. Use this skill when the user needs Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Installs and authenticates the GitHub CLI (gh) in a Claude.ai container, then runs gh commands against it. Use for "install gh", "gh auth", "create an issue or PR from the CLI", "gh is not authenticated", or any GitHub operation you want to issue as a gh command rather than a raw API call. This skill is the transport rather than the analysis. To understand what a repository does or contains, use exploring-codebases; to add a repo to the session, accessing-github-repos.

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

Use when the user wants to capture a writer's voice from a few sample articles and rewrite text to sound like that author — "蒸馏文风", "提炼XX的风格", "把这篇改成XX的味儿", "学某某笔法改写", "mimic this writer", "match this author's style", "style transfer". Works for any author, 王建硕 included.

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

Security best practices for Micronaut/Kotlin backend including authentication, authorization, input validation, and OWASP prevention. Use when implementing auth, validating inputs, or reviewing security.

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

Reviews application security and guides AppSec design. Use when reviewing auth, authentication, authorization, sessions, data handling, supply chain, or AppSec architecture.

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

Capture or review how this project connects to external systems (GitHub, AWS, npm, SSH, etc.) so future sessions know the auth recipe. Auto-detection hook logs candidate captures to an inbox; this skill promotes them to permanent recipes in `.planning/AUTH-RECIPES.md` and optionally to user-global memory at `~/.claude/auth-recipes/`.

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

Author learning targets for a competency across developmental bands with precise, observable progression language. Use when writing 'I can' statements for competency-based programmes.

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

Trigger.dev client/frontend surface: subscribe to runs in realtime (runs.subscribeToRun and the @trigger.dev/react-hooks hook useRealtimeRun), consume metadata and AI/text streams in React (useRealtimeStream), trigger tasks from the browser (useTaskTrigger, useRealtimeTaskTrigger), and mint scoped frontend credentials with auth.createPublicToken / auth.createTriggerPublicToken. Load when wiring a frontend (React/Next.js/Remix) or backend-for-frontend to show live run progress, status badges, token streams, trigger buttons, or wait-token approval UIs. NOT for writing the backend task itself (streams.define / metadata.set is trigger-authoring-tasks territory); this is the consumer side.

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

Author and run a durable AI chat agent with chat.agent from @trigger.dev/sdk/ai: the per-turn run loop, why you MUST spread ...chat.toStreamTextOptions() first, returning a StreamTextResult vs calling chat.pipe(), the two server actions (chat.createStartSessionAction + auth.createPublicToken), and wiring useChat to useTriggerChatTransport. Load this when building, modifying, or debugging a chat backend (the agent task or its lifecycle hooks) or its React transport, when declaring typed tools or custom data parts, or when migrating a plain AI SDK streamText route to chat.agent.

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

Overview of the Neon platform for apps and agents, spanning Postgres, Auth, Data API, and the new services: Object Storage, Compute Functions, and AI Gateway. Use whenever "Neon" is mentioned for an overview of how to work with Neon and how to get started. Otherwise, the individual capabilities are the triggers: "object storage" or "S3-compatible storage", "serverless functions", "background jobs", or "run code near my database", "AI gateway", "LLM proxy", "model routing", or "call an LLM" → AI Gateway; "database", "Postgres", or "authentication" → Postgres and Auth.

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

Twitter/X Agent Operations SOP v2 — Rebuilt from real dual-account operations. Real data: • CN account: grew from 1,150 → 3,679 followers (~14 months), 1 tweet/day, OAuth1 direct post • EN account: Buffer API • Real incidents: cron silent-failed for 2 weeks unnoticed, analytics data off by 17×, thread performance worse than single posts What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily log after every tweet + weekly report every Monday • Pre-publish safety checklist (agent must pass before posting) • Content pool tracker (used/unused) + alert when ≤3 items remain • Dual-account credential separation (CN: OAuth1 / EN: Buffer API) • MASTER-STATUS.md as the single source of truth — read + write every session 🇨🇳 Twitter/X Agent 运营 SOP v2 — 基于真实双账号运营经验重写。 开局对话式收集 context、强制日报+周报、发推前红线自检、素材库追踪、双账号凭证分离、MASTER-STATUS.md 单一真相来源。 真实数据：中文账号从 1,150 粉增长至 3,679 粉（约14个月），1条/天。 Triggers: "twitter运营" | "推特agent" | "发推SOP" | "AI代运营" | "推文日报" | "素材库" | "Buffer API" | "OAuth1发推" | "twitter automation" | "tweet sop" | "推特涨粉"

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

Remix v2 meta/SEO, sessions, auth, and CSRF. Use when working with document head, cookie sessions, auth gates, or CSRF protection. Triggers on meta export (v2 array shape), links export, createCookieSessionStorage, commitSession, destroySession, requireUserId, remix-utils/csrf, remix-auth.

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

Integrate MCP servers into Claude Code plugins — covers .mcp.json configuration, plugin.json mcpServers field, server types (stdio, SSE, HTTP, WebSocket), environment variable expansion, tool naming conventions, OAuth and token authentication, security best practices, and testing workflows. Use when adding an MCP server to a plugin, configuring MCP authentication, debugging MCP tool discovery, setting up Model Context Protocol integration, or choosing between stdio and SSE transport types.

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

Use when building, extending, or debugging FastMCP v4 (or v3) Python MCP servers. Activates on FastMCP tool/resource/prompt creation, provider and transform implementation (CodeMode, Tool Search), auth setup (MultiAuth, PropelAuth, KeycloakProvider), client SDK usage, FastMCPApp and Generative UI server building, fastmcp-slim client-only installs, nginx reverse proxy deployment, Prefab Apps, OTEL observability, testing, and v3→v4 migration. Grounded in official FastMCP v4 docs plus locally-verified v3 gotchas — zero speculation.

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

Implement or change AuthCrunch portal refresh configuration, opaque token families, atomic rotation, replay revocation, issuance claims, store adapters, and portal lifecycle. Use for portal refresh tokens, not upstream OAuth token renewal.

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

Maintain local bcrypt and Argon2id password generation, prefixed imports, reusable hashing configuration/parser, duplicate detection, changes, resets, credential revocation, and authentication work equalization.

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

Maintain portal public signing-key discovery at .well-known/jwks.json, reusable admin API directive parsing, opt-in admin private-key export, KMS key serialization, asymmetric issuer selection, base-path routing, and JWT verification tests. Excludes upstream OAuth provider JWKS consumption.

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

Maintain AuthCrunch VERSION authority, versioned synchronization, patch/minor release commands, CI artifact identities, and GoReleaser publication. Use for version checks, release automation, or release preparation.

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