9,886 件 ・ 関連度順
概要と使いどころ
Identify and exploit Mass Assignment vulnerabilities in APIs. Use this skill when testing REST APIs or application forms that directly map user-supplied JSON or POST input to internal database objects. An attacker can inject undocumented variables (e.g., `is_admin`, `verified`) to illegally modify restricted properties.
日本語の概要は準備中です。原文の説明を表示しています。
AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence.
日本語の概要は準備中です。原文の説明を表示しています。
Deep API security assessment beyond surface scanning. Covers the full OWASP API Security Top 10 (2023): Broken Object Level Authorization (BOLA / IDOR), Broken Authentication, Broken Object Property Level Authorization (mass assignment + excessive data exposure), Unrestricted Resource Consumption, Broken Function Level Authorization (BFLA / vertical privilege escalation), Unrestricted Access to Sensitive Business Flows, Server-Side Request Forgery via API parameters, Security Misconfiguration, Improper Inventory Management (shadow/zombie/deprecated endpoints, v1/v2 drift), and Unsafe Consumption of third-party APIs. Works across REST, GraphQL, gRPC, SOAP, and MCP servers. Discovers APIs from OpenAPI/Swagger specs, GraphQL introspection, gRPC reflection, .well-known endpoints, JS bundles, and traffic capture. Uses kiterunner, ffuf, schemathesis, restler-fuzzer, openapi-fuzzer, graphql-cop, clairvoyance, batchql, inql, jwt_tool, postman, mitmproxy, and manual http(action="request", ...) payloads. Every technique includes actual payloads, commands, and verification logic. Chains from /pentester or /codebase when API endpoints are discovered, chains into /web-exploit when classic injection points are found in API parameters, chains into /post-exploit when RCE is achieved, and chains into /ai-redteam when an LLM/AI endpoint is discovered (chat APIs, completion endpoints, RAG search, agentic tool-use, MCP servers).
日本語の概要は準備中です。原文の説明を表示しています。
Generate interactive, animated, responsive HTML-based terminal simulators to showcase CLI commands, scripts, pipelines, or interactive workflows. Use this whenever you need to visually showcase a command line sequence, mock interactive CLI tools, or simulate code executions.
日本語の概要は準備中です。原文の説明を表示しています。
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
日本語の概要は準備中です。原文の説明を表示しています。
Phase 1 of the Gaia evidence verification pipeline. Use this skill whenever you need to gather, consolidate, or refresh raw evidence for named skills in the registry. Trigger phrases: "collect evidence", "populate the data lake", "gather sources", "run ev-collection", "Phase 1", "compile the evidence index", "refresh the unified lake", "aggregate skill evidence", "build the evidence database". Also invoke as the first step before running ev-star-verification, ev-adversarial-audit, or ev-link-validation — nothing downstream is meaningful without a fresh, compiled index. Covers GitHub repo links, stargazer signals, YouTube showcases, arXiv papers, peer reviews, benchmark results, blog/newsletter posts, and self-attestation artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect scope and unexpected registry drift against the actual PR base and leave a concise final receipt. Use for "check for drift", "wrap up the pipeline", or the final stage; never silently discard unknown changes or infer a clean diff from validator success.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive, reusable playbook for multi-component suite intake under Yggdrasil III. Audits component installability, maps origin candidates to generic capabilities, ingests named components with shared-repo baseline caps, manifests suites via gaia dev fuse, calibrates capstone and component ranks, and closes out via Class S regeneration.
日本語の概要は準備中です。原文の説明を表示しています。
Fine-tune large language models — data curation, SFT, parameter-efficient methods (LoRA), evaluation, and avoiding common training failures. Use when a base model needs task-specific behavior or domain knowledge.
日本語の概要は準備中です。原文の説明を表示しています。
Work with text embeddings — choosing models, pooling, similarity measures, evaluation, and multilingual considerations. Use when building semantic search, clustering, or any similarity-based feature.
日本語の概要は準備中です。原文の説明を表示しています。
Screening for drug-drug interactions — mechanistic prediction, database checks, and clinical risk assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Design role-based agent teams with CrewAI — agents, tasks, crews, and collaboration patterns for complex workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Relational schema design — normalization, keys, constraints, and evolution — use when modeling data or reviewing a schema.
日本語の概要は準備中です。原文の説明を表示しています。
Get productive with agentic coding assistants — task framing, iterative prompting, file-scoped workflows, review loops, and multi-file refactors. Use when pairing with an AI coding agent on real codebases.
日本語の概要は準備中です。原文の説明を表示しています。
Ship iOS/Android apps with Capacitor: web codebase, native plugins, live updates, and store builds. Use when wrapping a web app as native mobile apps.
日本語の概要は準備中です。原文の説明を表示しています。
Configure Babel: presets, plugins, env-specific builds, polyfills, and performance. Use when maintaining Babel-based toolchains or writing custom transforms.
日本語の概要は準備中です。原文の説明を表示しています。
Build on AWS with Amazon Bedrock — managed foundation models, agents, knowledge bases, and guardrails.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate teams of role-based agents — role definitions, task delegation, sequential and hierarchical workflows, and shared memory. Use when a job naturally splits into specialist roles collaborating.
日本語の概要は準備中です。原文の説明を表示しています。
Run ABM programs — target account selection, personalized campaigns, sales orchestration, and account-level measurement.
日本語の概要は準備中です。原文の説明を表示しています。
Complete B2B SaaS marketing agency powered by 90 AI agents across 17 specialties. This is the entry point for ALL marketing requests. Routes to the right specialist team: content marketing, SEO, paid media, social media, email marketing, design, sales enablement (including technical presales — demos, proofs of concept, security questionnaires), product marketing, account-based marketing (ABM), partnerships and channel programs (co-marketing, marketplace GTM, channel conflict and deal registration, partner economics), growth, analytics, project management, or client operations. Use this skill when the request spans multiple disciplines or when unsure which specialist to invoke. Also triggers on: marketing help, marketing team, marketing agency, what can you do, marketing capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Product-led growth and customer-base growth for B2B SaaS. Use this skill for self-serve funnel work (activation, time-to-value, free trial vs freemium, PQL definition, in-product upgrade moments, sales-assist triggers), for the self-guided interactive product demo that runs in front of the login wall (demo portfolio and flow design, gated vs ungated policy, demo seed data and privacy, keeping a published demo in sync with the shipping product, step-level demo analytics), and for growing revenue from existing customers (adoption, expansion, churn-save, the self-serve cancel flow and failed-payment recovery, renewal marketing, net revenue retention, and champion tracking: watching the people who bought and used you at each customer, confirming a job change from evidence, and running both plays a move fires, the seat they left and the account they joined). Also triggers on: PLG, product-led growth, activation, aha moment, time to value, free trial, freemium, PQL, product qualified lead, onboarding, self-serve, customer marketing, expansion revenue, upsell, cross-sell, churn, retention, NRR, renewal, cancel flow, cancellation flow, save offer, exit survey, pause subscription, dunning, failed payment recovery, involuntary churn, people keep canceling, champion tracking, job change signals, job change alerts, our champion left, our champion changed jobs, customer alumni, former customers who moved to a new company, interactive demo, self-guided demo, product tour, click-through demo, demo automation, demo library, should our demo be gated, ungated demo, demo without a sales call, our demo is out of date, demo shows the old UI, put a demo on our homepage, demo completion rate, demo drop-off, try before you talk to sales.
日本語の概要は準備中です。原文の説明を表示しています。
Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a customer referral program (who may accept the reward, how the introduction is made), designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for an early-stage startup where the founder is still doing the selling — running founder-led sales, setting up a design-partner program, judging whether you have product-market fit, deciding what not to do yet, deciding when to hire the first AE or first marketer, and moving upmarket to larger buyers. Also use it when your company has just acquired another (or is about to), to plan the marketing integration: what you may and may not do between signing and close, the first letter to the acquired customers, whether to keep, endorse, fold in or retire the acquired brand, merging the two marketing databases without mailing people who opted out, when to start cross-selling, and announcing a product sunset. Also use it to design a demand-generation campaign and the channel plan it runs on: one campaign with one job, the offer for buyers who are and are not in market, what each channel is for, the kill and scale rules set before launch, the follow-up sales agrees to, the yearly calendar of always-on programs and tentpole campaigns, and which channels to keep, test or stop. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: founder-led sales, founder-led GTM, design partners, design partner agreement, first customers, first 10 customers, do we have product-market fit, PMF, Sean Ellis test, very disappointed survey, pre-seed, seed stage, when to hire our first AE, first sales hire, first marketing hire, moving upmarket, going upmarket, enterprise readiness, first enterprise deal, what do enterprise buyers need before they sign, positioning, product launch, beta program, early access program, design partners, private preview, public preview, general availability, GA launch, when can we call it GA, can sales sell a beta feature, selling the roadmap, launch tier, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, ideal customer profile, ICP, what is our real ICP, who actually buys from us, refresh our ICP from closed-won deals, ICP refresh before planning, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget. Also triggers on public-sector marketing: sell to government, government marketing, public sector go-to-market, federal marketing, state and local government, SLED, FedRAMP, FedRAMP marketing claims, can we say FedRAMP ready, GovRAMP, StateRAMP, VPAT, accessibility confor
日本語の概要は準備中です。原文の説明を表示しています。
Keep paperclip-docs in lockstep with the parent paperclipai/paperclip codebase. Detects code-surface changes (CLI, env vars, API routes, adapters, plugin SDK, schemas) and produces friendly-tutorial-voice doc updates. Two modes — `nightly` (tracks parent's default branch (currently `master`), targets the `nightly` branch, preview deploy) and `release` (on parent tag, merges nightly → main, tags, ships live). Trigger phrases: "sync docs", "update docs from paperclip", "/sync-docs", "check for paperclip changes", "is docs current".
日本語の概要は準備中です。原文の説明を表示しています。
Plan a feature before writing any code. Use this skill at the START of non-trivial feature work — when the user says they want to "add", "build", "implement", "create", "develop", or "ship" a feature, endpoint, component, page, service, or capability. Especially trigger when the user's prompt is short or under-specified ("add a dashboard", "build an auth flow", "let's do user activity reports") — those need planning, not direct execution. The skill walks through requirements clarification, codebase exploration, sketches a Mermaid architecture/flow diagram of the proposed design, and produces a plan.md document the user can hand off to a fresh AI session for execution. Skip only when the change is genuinely trivial (typo fixes, single-line tweaks, renames). When in doubt, plan.
日本語の概要は準備中です。原文の説明を表示しています。