1,083 件 ・ 関連度順
概要と使いどころ
Identify and map the external corporate footprint of a target organization. Use this skill at the absolute beginning of an engagement (Reconnaissance) to identify all registered domains, subdomains, IP ranges, and Autonomous System Numbers (ASNs) owned by the target. This skill forms the foundation for all subsequent external penetration testing and attack surface management.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 3 of the feature-pipeline suite. Use this after /fp-plan has received explicit user approval and printed the M2-plan stop hook — when you need to translate an approved numbered plan into committed, pushed code. Triggers on: "implement the plan", "start coding", "commit the plan", "write the code", "fp-implement", "Phase 3", "plan is approved let's code", "next step after plan", "execute the plan", "apply the plan", "make the changes". Reads planApproved and branch from state; refuses to run if approval hasn't been recorded. Commits one atomic change per plan step, pushes after each commit, handles obstacles cleanly, and hands off to /fp-review when done. Never squashes or skips steps — the one-commit-per-step rule keeps the review history readable and rollback surgical.
日本語の概要は準備中です。原文の説明を表示しています。
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive social media operations for B2B SaaS brand building and engagement. Use this skill to develop LinkedIn strategy, decide whether to run a LinkedIn newsletter and how to scope it, capture consented registrations from LinkedIn Events, check LinkedIn Live eligibility, manage Twitter/X presence, create YouTube content, engage on Reddit communities, decide whether and how to answer on Quora, build community, develop influencer and creator partnerships, vet a creator before paying them, start or fix a B2B podcast, book podcast guests and guest appearances, judge whether a podcast is worth appearing on when you cannot audit its numbers, write show notes and transcripts, run social listening (what are people saying about us, share of voice, brand monitoring, validated sentiment, alert thresholds, routing signals to the right owner), and execute organic social campaigns. Also triggers on: LinkedIn, LinkedIn newsletter, LinkedIn Events, LinkedIn Live, event registration form, subscribe to our newsletter on LinkedIn, marketing consent checkbox, Notify Employees, Twitter/X, YouTube, Reddit, community, influencer, creator partnerships, influencer vetting, engagement rate, fake followers, engagement pods, FTC disclosure, sponsored post disclosure, media kit, social media strategy, organic social, employee advocacy, podcast, podcast strategy, podcast guesting, how do I know if this podcast has real listeners, the host says they get 50k downloads, is this podcast worth going on, podcast RSS feed research, IAB podcast measurement certification, Listen Score, Apple Podcasts reviews, show notes, audiogram, episode transcript, social media account access, who has admin on our LinkedIn page, the person who ran our social accounts left, locked out of our company account, social media offboarding, YouTube channel owner, Slack primary owner, social account MFA, social media approval workflow, pause all scheduled posts, social listening, what are people saying about us, brand monitoring, brand mentions, share of voice, social share of voice vs competitors, sentiment analysis, is our sentiment dashboard accurate, listening query, boolean query, mention alerts, spike alert, CrowdTangle replacement, Reddit API access, which platforms can our listening tool see, someone on Reddit asked for a tool like ours, comment mining, voice of customer from social.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Emergency Management Director — activating and staffing an EOC for a developing hazard, sequencing a disaster declaration and FEMA Public Assistance/Individual Assistance request, sizing shelter and resource needs against real population and capacity numbers, designing or critiquing a tabletop exercise, or writing an after-action report and improvement plan.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a drywall and ceiling tile installer — specifying a fire-rated wall/ceiling assembly to a UL design number, hitting an STC target on a demising wall, choosing board type for a wet area, placing control joints on a long run, or diagnosing why a finished assembly failed inspection or a sound/mold complaint.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Electrical and Electronics Drafter — sizing a conductor and conduit for a panel or feeder circuit against NEC ampacity and fill tables, building a schematic/elementary diagram or one-line diagram on IEEE 315/ANSI Y32.2 symbols, cross-referencing wire numbers between a schematic and a panel wiring diagram, sizing a PCB trace against IPC-2221 current tables, or QC-checking an electrical drawing set before issuance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Data Warehousing Specialist — defining the grain of a fact table before modeling it, choosing a slowly changing dimension (SCD) type for a dimension attribute, designing an incremental ETL/ELT load strategy against a full-refresh alternative, resolving a conformed-dimension conflict across source systems, or diagnosing why a BI report's numbers don't reconcile to the source system.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Business Intelligence Analyst — reconciling a metric discrepancy between reports, designing a dimensional model or semantic layer for self-service dashboards, setting a data freshness/latency SLA, or diagnosing why a dashboard's aggregate number is misleading.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a choreographer — building and teaching a dance number against a rehearsal-hour budget, staging repertory under a trust/estate's licensing rules, planning a tech-week spacing and cueing schedule, or diagnosing why a piece isn't reading from the audience.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a radio broadcast announcer or on-air disc jockey — backtiming a live break against a hard network join or legal ID, deciding what to cut when a caller or breaking-news read runs long, judging FCC indecency/EAS exposure on live content, structuring a voice-tracked shift so it doesn't read as canned, or diagnosing why a daypart's PPM numbers are sliding.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Architectural and Civil Drafter — setting up a CAD sheet at the correct scale and viewport scale factor, applying NCS/AIA layer and sheet-numbering standards, dimensioning a wall assembly or site plan per governing convention, managing xrefs and revision clouds across a sheet set, or QC-checking a drawing set before issuance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Aerospace Engineering and Operations Technologist/Technician — verifying an installed fastener's preload against a drawing's torque callout via the T=K·D·F relationship, reducing strain-gauge data from a structural proof-load test into stress and checking it against an FEA-predicted margin, selecting and executing an NDI method against a defect type and material, reducing a wind-tunnel test point's dynamic-pressure and Reynolds-number data, or ballooning and dispositioning an AS9102 first article inspection. Distinct from an aerospace-engineer (owns the design, structural analysis, and certification basis) — this role builds, instruments, tests, and inspects the hardware the engineer specified, closing the loop with measurement rather than deriving a new analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-agent review resolution with trust-but-verify methodology. Accepts a PR number/URL or a local code-review report file. Extracts review comments, verifies each with parallel agents using confidence scoring (0-100), filters false positives, presents a triage report for approval, then applies fixes and replies. Use when user runs /resolve-review, mentions "resolve PR comments", "address review feedback", "fix PR suggestions", "handle review comments", or "resolve review findings".
日本語の概要は準備中です。原文の説明を表示しています。
Create, review, and manage Architecture Decision Records (ADRs) with auto-numbering, template detection, quality review, and index maintenance. Use when user mentions "ADR", "architecture decision", "document this decision", "create ADR", "review ADR", editing ADR files (docs/adr/, doc/adr/, .adr/), or discussing architectural choices and tradeoffs.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold, validate, and maintain Johnny.Decimal documentation structure for software projects. Use when user mentions "Johnny Decimal", "J.D docs", "docs structure", "organize docs", "documentation layout", "scaffold docs", "docs migration", "generate index", "docs index", "add area", "classify docs", "move doc", editing files in numbered directories (00-*, 10-*, 20-*), or discussing documentation organization.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing Lamport-style hierarchical mathematical proof forward for validity and whether its hierarchy, scope, dependencies, side conditions, and proof constructs discharge the stated theorem. Use when the central question concerns a top-down proof with numbered levels, subproofs, ASSUME/PROVE, SUFFICES, PICK, CASE, DEFINE, Q.E.D., or prose equivalents. For an ordinary proof that first needs source-preserving hierarchy, use convert-lamport; for conclusion-first AND/OR obligation reconstruction, use reverse-lamport. Do not use to generate or replace a proof, or to audit Lean, Coq, Isabelle, or other proof-assistant source.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
日本語の概要は準備中です。原文の説明を表示しています。
Search DigiKey by keyword or part number, check stock and price breaks, retrieve component specifications, and download or synchronize datasheets for an electronics project. Use when the user explicitly wants DigiKey data, a DigiKey prototype-order comparison, or direct datasheet synchronization. For distributor-neutral sourcing, multi-vendor price comparison, or order-file generation, use the bom skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Build and deploy Flutter apps to App Store (TestFlight) and Google Play (internal/production). Auto-detects project structure, pulls signing secrets from AWS Secrets Manager, installs certificates, bumps build numbers, and runs Fastlane. Fully autonomous.
日本語の概要は準備中です。原文の説明を表示しています。
Set up mobile CI/CD pipelines for Flutter, React Native, or native iOS/Android — GitHub Actions workflows for testing, code signing, TestFlight/Play Store distribution, build number management, Fastlane integration, and artifact retention
日本語の概要は準備中です。原文の説明を表示しています。
Monitor federal grant opportunities across Grants.gov (Simpler.grants.gov is the modern UX), SAM.gov assistance listings (the post-CFDA replacement that preserves CFDA program numbers), and direct agency portals — NIH RePORTER + NIH Guide, NSF Funding, DOE OSTI, USDA NIFA, EPA Grants.
日本語の概要は準備中です。原文の説明を表示しています。