Business logic flaws are application vulnerabilities where valid functions are abused in unintended ways: price manipulation via hidden field tampering, workflow step-skipping, function call limit bypass (coupon reuse), process timing exploitation (race conditions on balance updates), and request forging via guessable/predictable parameters. Detect using Burp Suite proxy interception, HTTP POST/GET parameter analysis, and misuse-case testing against multi-step workflows. Tools: Burp Suite, OWASP ZAP.
日本語の概要は準備中です。原文の説明を表示しています。
ShulkwiSEC/bb-huge☆ 242026年7月11日 更新
Identify and exploit flaws in the core business rules and logic of web applications. This skill focuses on manipulation of application workflows, pricing, inventory limitations, and multi-step processes. Use this skill when bug hunting or testing e-commerce, banking, or SaaS platforms where standard technical vulnerabilities (e.g., XSS/SQLi) are not present but the application's logic is flawed.
日本語の概要は準備中です。原文の説明を表示しています。
ShulkwiSEC/bb-huge☆ 242026年7月11日 更新
Application-level business logic security testing for any domain. Takes an understanding-first approach: map the intended workflows before probing them. Covers: value/quantity logic abuse (negative, zero, overflow, rounding on any numeric field), workflow and state machine bypass (skipping required steps, forcing illegal state transitions, reusing one-time tokens), trust boundary violations (BOLA horizontal/vertical, BFLA, cross-tenant access, negative ownership attacks), idempotency and replay attacks (duplicate submissions, double-spend, same-reference reuse), multi-step flow integrity (checkout, registration, approval, verification), quota and rate limit bypass, time/date manipulation, and authorization code / reference number predictability. Domain-agnostic — applies to SaaS, e-commerce, banking, gaming, social platforms, APIs, or any multi-user application with stateful workflows. Chains from /pentester; chains into /param-fuzz when boundary violations or mass assignment are confirmed.
日本語の概要は準備中です。原文の説明を表示しています。
ShulkwiSEC/bb-huge☆ 242026年7月11日 更新
Entry P1 category router for business logic testing. Use when workflow abuse, race conditions, pricing flaws, or multi-step state attacks matter more than parser-level input injection.
日本語の概要は準備中です。原文の説明を表示しています。
ShulkwiSEC/bb-huge☆ 242026年7月11日 更新
Business logic vulnerability playbook. Use when reasoning about workflows, race conditions, price manipulation, coupon abuse, state machines, and multi-step authorization gaps.
日本語の概要は準備中です。原文の説明を表示しています。
ShulkwiSEC/bb-huge☆ 242026年7月11日 更新
Test AI agent systems for tool abuse, unauthorized actions, privilege escalation through tool chaining, and safety bypass via agentic workflows. Use this skill when assessing autonomous AI agents that use tool-calling (function calling, plugins, actions) to interact with external systems. Covers multi-step attack chains, implicit trust exploitation, and capability boundary testing for AI agents.
日本語の概要は準備中です。原文の説明を表示しています。
ShulkwiSEC/bb-huge☆ 242026年7月11日 更新
Active Directory ACL abuse playbook. Use when exploiting misconfigured AD permissions including GenericAll, WriteDACL, DCSync rights, shadow credentials, LAPS reading, GPO abuse, and BloodHound-guided attack paths.
日本語の概要は準備中です。原文の説明を表示しています。
ShulkwiSEC/bb-huge☆ 242026年7月11日 更新
Hunts for domain fronting and CDN abuse by detecting TLS SNI versus HTTP Host header mismatches and high-reputation CDN domains carrying anomalous traffic in network telemetry. Activates for requests to hunt domain fronting, detect SNI/Host mismatch, or find CDN abuse used to mask C2.
日本語の概要は準備中です。原文の説明を表示しています。
meltedinhex/analyst-ai-pack☆ 222026年7月7日 更新
Use when a task needs the judgment of a Business Continuity Planner — running a business impact analysis (BIA) to derive recovery time objectives, mapping process dependencies to find single points of failure, evaluating whether current recovery capability meets a process's maximum tolerable downtime, designing or debriefing a tabletop exercise, or building the cost-benefit case for a continuity investment.
日本語の概要は準備中です。原文の説明を表示しています。
wonsukchoi/domain-experts☆ 212026年10月12日 更新
Set up and operate a Shopify store with Shopify's official MCP server (the installed `shopify` command, NOT the npm Shopify CLI). Use whenever someone wants to sell online, start an online store or business, try Shopify, or manage a Shopify store — even if they do not say "Shopify": "I want to sell candles online", "help me start an online business", "open my first store", "add products", "check my orders", "set inventory", "make a discount", "show my sales", "how did my Shopify Email campaigns do". Before connection it can show relevant mock.shop sample catalogs, suggest business names, check domains, search shopify.dev, and validate GraphQL. The connect flow can create an account and store for a new user. Do the work here rather than only listing setup steps. Keywords: Shopify MCP, ecommerce, sample products, demo store, starter catalog, ShopifyQL, first store, create product.
日本語の概要は準備中です。原文の説明を表示しています。
obra/muse-skills☆ 202026年10月13日 更新
Build a structured Quarterly Business Review deck for a customer account. Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck", "renewal prep", "executive check-in", "90-day review", or "customer business review" - even if they don't use the acronym. Applies to CSMs preparing for executive-level customer meetings focused on value delivered, health, and next quarter alignment.
日本語の概要は準備中です。原文の説明を表示しています。
qa-aman/claude-skills☆ 202026年10月13日 更新
Documenting As-Is and To-Be business processes for a Salesforce project as swim-lane diagrams — one lane per actor, explicit decision points, parallel and exception/sad paths, and per-step automation-tier annotations that drive downstream build decisions. Trigger keywords: As-Is To-Be salesforce process, swim lane salesforce, business process map, automation candidate identification, sad path documentation, process actor mapping, manual residue. NOT for Opportunity stage and exit-criteria design — use admin/sales-process-mapping. NOT for picking Flow vs Apex for one requirement — use admin/process-automation-selection.
日本語の概要は準備中です。原文の説明を表示しています。
PranavNagrecha/AwesomeSalesforceSkills☆ 192026年10月4日 更新
Use when configuring or troubleshooting a Salesforce B2C Commerce (SFCC) storefront — including Business Manager site creation, SFRA cartridge path setup, customer groups, search index rebuilding, and key quota limits. Trigger keywords: SFCC, Commerce Cloud, Business Manager, storefront, cartridge, SFRA, site preferences, replication. NOT for B2B Commerce on Lightning (WebStore, BuyerGroup) — use admin/b2b-commerce-store-setup. NOT for choosing SFCC vs B2B Commerce — use architect/b2b-vs-b2c-architecture.
日本語の概要は準備中です。原文の説明を表示しています。
PranavNagrecha/AwesomeSalesforceSkills☆ 192026年10月4日 更新
Review approved Grafana business-intelligence evidence for revenue, conversion, and operational KPIs. Use for bounded KPI scorecards, financial or operational metric checks, baseline comparisons, and business-unit reviews without changing source systems.
日本語の概要は準備中です。原文の説明を表示しています。
openai/community-plugins☆ 152026年10月13日 更新
Padrões especializados para implementação de busca Algolia, estratégias de indexação, React InstantSearch e ajuste de relevância. Use quando: adicionar busca, algolia, instantsearch, search api, funcionalidade de busca.
日本語の概要は準備中です。原文の説明を表示しています。
artubss/SKILLS-CLAUDE-CODE☆ 112026年5月17日 更新
Biblioteca do Facebook para busca eficiente de similaridade e clustering de vetores densos. Suporta bilhões de vetores, aceleração GPU e vários tipos de índice (Flat, IVF, HNSW). Use para busca k-NN rápida, recuperação de vetores em larga escala ou quando você precisa de busca pura de similaridade sem metadados. Melhor para aplicações de alto desempenho.
日本語の概要は準備中です。原文の説明を表示しています。
artubss/SKILLS-CLAUDE-CODE☆ 112026年5月17日 更新
[Content] Use when you need to evaluate business idea viability: Business Model Canvas, financial projections, risk matrix, go-to-market, execution plan.
日本語の概要は準備中です。原文の説明を表示しています。
duc01226/EasyPlatform☆ 112026年8月21日 更新
Detect command injection attacks against Modbus TCP/RTU protocol in ICS environments by monitoring for unauthorized write operations, anomalous function codes, malformed frames, and deviations from established communication baselines using ICS-aware IDS and protocol deep packet inspection.
日本語の概要は準備中です。原文の説明を表示しています。
andycungkrinx91/konoha☆ 92026年10月9日 更新
Detect and investigate Azure service principal abuse including privilege escalation, credential compromise, admin consent bypass, and unauthorized enumeration in Microsoft Entra ID environments.
日本語の概要は準備中です。原文の説明を表示しています。
andycungkrinx91/konoha☆ 92026年10月9日 更新
Detect dangerous ACL misconfigurations in Active Directory using ldap3 to identify GenericAll, WriteDACL, and WriteOwner abuse paths
日本語の概要は準備中です。原文の説明を表示しています。
andycungkrinx91/konoha☆ 92026年10月9日 更新
事業計画書を体系的に作成するスキル。新規事業、既存事業の拡大、スタートアップのピッチ資料、 社内新規プロジェクト提案など、あらゆる事業計画のドキュメントを構造化して作成する。 「事業計画」「ビジネスプラン」「business plan」「新規事業提案」「事業企画」「収支計画」 「プロジェクト提案書」「投資計画」「起業」「創業計画」などのキーワードが出たら必ずこのスキルを使用する。 事業のアイデア段階から、市場分析、競合分析、収支シミュレーション、リスク評価まで 包括的にカバーする。日本語・英語の両方に対応。
takusaotome/claude-skills-library☆ 92026年10月5日 更新
Turns a business need and its constraints into a DRAFT RFP requirements pack: traced functional and non-functional requirements with priorities, mandatory gates, evaluation criteria with weights left to the business owner, and fact-seeking supplier questions. Solution-neutral; never names a supplier or product. Use when the user asks to "write the RFP requirements", "turn this business case into tender requirements", "draft the supplier questionnaire", "structure our RFQ from this brief" or "set up evaluation criteria before we go to market". Do not use for responses already received, use rfp-comparison-pack to compare them or supplier-evaluation-matrix to score them instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
kesslernity/awesome-copilot-agent-skills☆ 82026年9月19日 更新
Assembles a DRAFT capital expenditure request pack from the requester's inputs: business need, options including do nothing, costs exactly as provided, benefits as stated, risks, assumptions, budget status and the approvals route read from the organisation's own delegation of authority, with UNKNOWN for every missing figure, date or name. Use when the user asks to "prepare a capex request", "draft the business case for this equipment", "fill in the capital request form", "structure this investment proposal" or "what approvals does this spend need". Do not use for a board or committee decision paper, use board-paper-skeleton instead; for an IT change approval, use change-request-pack; to pressure-test a finished business case, use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
kesslernity/awesome-copilot-agent-skills☆ 82026年9月19日 更新
Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri...
日本語の概要は準備中です。原文の説明を表示しています。
netbarros/psique☆ 62026年4月22日 更新