Secure AI coding agents (Claude Code, Cursor, Codex, Copilot) with permission boundaries, secret protection, code review gates, and safe sandbox configurations for team environments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
1.1천건 · 관련도순
Secure AI coding agents (Claude Code, Cursor, Codex, Copilot) with permission boundaries, secret protection, code review gates, and safe sandbox configurations for team environments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Access matrix of role-by-module permissions, with per-role scope, confidentiality level and SME tier, as CSV, SQL, JSON Schema or Notion on request. Use for access reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound) with trigger, step timing, branch/exit conditions, goal, frequency governance (send caps, quiet hours, fatigue guardrail), a sunset path, and a SEND N-dimension score. Not for the closed-loop win-back / re-consent (re-permission) program on a lapsed cohort — use reactivation-specialist; not for writing each email's copy — use email-creative-builder; not for computing EQS or the N1 unsubscribe veto — use email-quality-auditor. 邮件自动化流程设计/购物车挽回/流失召回序列
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to register/query a social channel, record channel state, cadence, governance, voice adaptation, UGC permission, or advocacy facts; curates them through the append-only channels event stream and derived views. Not for ECHO scoring — use social-quality-auditor; not for channel selection — use channel-portfolio-planner. 渠道台账/账号档案/UGC授权记录
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan agent skills for security issues before adoption. Detects prompt injection, malicious code, excessive permissions, secret exposure, and supply chain risks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects tables created without ROW LEVEL SECURITY enabled, over-permissive policies (USING (true) / WITH CHECK (true) without owner conditions), and service_role key exposure in client code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews GitHub Actions workflow diffs for script injection of untrusted input, pull_request_target with untrusted checkout, over-broad GITHUB_TOKEN permissions, and unpinned third-party actions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects over-permissive Firestore/Storage rules (allow read, write: if true / auth-only without ownership), missing auth checks on writes, and admin SDK private key exposure to client bundles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI-driven Flutter E2E testing via VM Service CLI. Control running Flutter apps in debug mode for smoke tests, regression checks, exploratory testing, and UI automation. Trigger when user mentions E2E testing, UI automation, smoke tests, integration testing, test automation, controlling Flutter apps, VM Service interaction, debugging UI flows, automated regression testing, CI sanity checks, or testing native dialogs/permissions/WebViews. Supports stateful named instances or stateless direct URI connections. Ideal for rapid test feedback, AI agent workflows, element discovery, screenshot capture, log collection, and scriptable UI interactions (tap, scroll, enterText). Use for troubleshooting flaky tests, automating repetitive manual tests, verifying app behavior after merges, or setting up automated QA pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Covers Flutter testing across all three layers: unit tests (business logic, ViewModels, repositories), widget tests (UI rendering, interactions, golden regression), and integration/E2E tests (full app flows, native OS interactions). Use this skill when writing any Flutter test, setting up mocking with mocktail or mockito, implementing golden file tests, debugging async failures (pumpAndSettle timeouts, Timer leaks, FakeAsync deadlocks), fixing cross-platform golden pixel diffs in CI/CD, testing state management (Riverpod/BLoC/Provider), handling permission dialogs or native system UI with Patrol, or troubleshooting MediaQuery/Theme missing errors in widget tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map and attack the authentication, authorization, session, tenant, federation, and machine-identity boundaries of a system, proving whether access controls actually hold rather than whether they appear to. Use whenever work touches login, sessions, tokens, roles, permissions, multi-tenancy, password reset, invitations, OAuth/OIDC/SAML, API keys, service accounts, webhooks, admin impersonation, or any question of "can this actor do or see this thing." Prefer this over a generic security pass for identity-heavy surfaces. Part of the audit suite; inherits the shared constitution while its own job is proving or disproving access boundaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds native iOS apps in Swift — SwiftUI and UIKit screens, state and data flow, NavigationStack, lists, forms and accessibility; networking with URLSession and Codable, persistence with SwiftData, Core Data, files and the Keychain; permissions, push notifications, universal links, background tasks, widgets, App Intents and StoreKit 2 purchases; performance with Instruments and MetricKit; and release with signing, TestFlight and App Store Connect. Use when writing or changing native iOS code, adding a platform feature, preparing a build for TestFlight or the App Store, or when the user asks how to do something on iOS, even if they do not name the framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds React Native and Expo apps in TypeScript — navigation with React Navigation or Expo Router, lists, forms, styling, gestures and animations with Reanimated, safe areas, accessibility and localization; networking with TanStack Query, response validation, persistence with MMKV, AsyncStorage, SQLite and secure storage; permissions, push notifications, deep links, background tasks, native modules and config plugins; performance with Hermes and the React profiler; and release with EAS Build, EAS Submit and EAS Update or bare Gradle and Xcode builds. Use when writing or changing React Native code, adding a native capability, configuring Expo, preparing a store build or an over-the-air update, or when the user asks how to do something in React Native, even if they do not name the library.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Upsy for secure access to third-party accounts and tasks involving memory, files, connected email, calendar, documents, messaging, project apps, and the cloud browser. Guide account connections, scoped permissions, and activity auditing, even when the user has not mentioned Upsy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool ...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when implementing, modifying, configuring, or debugging Capacitor native plugins, permissions, or Android/iOS integrations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 Chamber — chamber secrets management using AWS Systems Manager Parameter Store, service-scoped secret organization, environment variable export, and parameter auditing. Covers reading and writing secrets by service, comparing environments, listing services, version tracking, and IAM permission validation. Use when managing AWS SSM-based secrets with Chamber, auditing parameter changes, or comparing configs across services.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Box — box cloud content management platform covering files, folders, users, collaborations, metadata, and usage analytics. Use when monitoring storage usage, analyzing file activity, reviewing collaboration health, managing Box users and permissions, or troubleshooting content sharing issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.