559 件 ・ 関連度順
概要と使いどころ
STIX 2.1 bundle creation reference. Object types, relationships, and JSON templates for structured threat intelligence sharing. Includes the per-claim mapping of evidence grades (access level and claim support) from /quality-of-information-check to STIX confidence, and the reverse mapping on import.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to query an OpenCTI instance — is this IOC already known, what entities/reports/campaigns exist for an actor — or push new intel into it — creating indicators/observables, labelling, TLP markings, relationships, or importing a STIX 2.1 bundle. Two-way integration. Commonly invoked by /ip-investigation and friends to check whether an indicator is already in your knowledge base, and by analytical skills that want to publish their findings back to OpenCTI. Reads $OPENCTI_URL and $OPENCTI_TOKEN.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive framework for effective gptme agent onboarding that builds user trust, communicates capabilities clearly, and establishes productive working relationships from the first interaction.
日本語の概要は準備中です。原文の説明を表示しています。
Manage knowledge graph for autonomous coding. Use when storing relationships, querying connected knowledge, building project understanding, or maintaining semantic memory.
日本語の概要は準備中です。原文の説明を表示しています。
Executes authorized attack simulations against Active Directory environments to identify misconfigurations, weak credentials, dangerous privilege paths, and exploitable trust relationships that could lead to domain compromise. The tester uses BloodHound for attack path analysis, Mimikatz for credential extraction, and Impacket for protocol-level attacks including Kerberoasting, AS-REP Roasting, and delegation abuse. Activates for requests involving Active Directory pentest, AD attack simulation, domain compromise testing, or Kerberos attack assessment.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Giddens' structuration theory to analyze the duality of structure — how social structures are both the medium and outcome of the practices they organize. Use this skill when the user needs to bridge agency and structure in organizational or social analysis, explain how routines reproduce or transform institutional patterns, analyze the recursive relationship between action and structure, or when they ask 'do people shape institutions or do institutions shape people', 'how are these routines maintained', or 'where does change come from if structures constrain action'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Transaction Cost Economics (Williamson, 1975, 1985) to analyze governance structure choices — market, hybrid, or hierarchy — based on transaction characteristics. Use this skill when the user needs to decide make-or-buy, evaluate outsourcing vs vertical integration, design governance mechanisms for inter-firm relationships, or when they ask 'should we build this in-house or outsource', 'why do firms vertically integrate', or 'how should we structure this partnership'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Co-opetition Value Net framework (Brandenburger and Nalebuff, 1996) to map cooperative and competitive dynamics in business relationships. Use this skill when the user needs to identify complementors, analyze the PARTS framework, or design strategies that simultaneously cooperate and compete with the same players.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Granovetter's embeddedness theory to analyze how economic behavior is embedded in ongoing social relations, avoiding both over-socialized and under-socialized accounts. Use this skill when the user needs to explain why market transactions deviate from pure economic rationality, analyze how trust and social ties shape business dealings, evaluate structural vs relational embeddedness in inter-firm networks, or when they ask 'why do firms prefer existing partners over cheaper alternatives', 'how do social relationships shape economic outcomes', or 'is this market truly arms-length'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Hierarchical Linear Modeling (HLM) to analyze nested data structures with random intercepts and slopes, accounting for intra-class correlation and cross-level interactions. Use this skill when the user has students nested in schools, employees in firms, or repeated measures in individuals, needs to partition variance across levels, or when they ask 'how do I handle nested data', 'what is ICC', or 'do group-level factors moderate individual-level relationships'.".
日本語の概要は準備中です。原文の説明を表示しています。
Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.
日本語の概要は準備中です。原文の説明を表示しています。
"Customer relationship management strategy — integrated framework with six pillars: customer segmentation (RFM/CLV), journey orchestration (cross-channel), CDP technology stack, loyalty-program design, B2B key-account management (KAM), and CRM organization/governance. Use for VIP program design, membership-system decision, retail/ecommerce/B2B customer strategy, CDP buy-vs-build, marketing-automation adoption, or key-customer churn. Triggers: 『CRM 系統』『會員經營』『客戶分級』『大客戶策略』『CDP』『行銷自動化』『客戶生命週期』『VIP 方案』『顧客忠誠』『RFM』『CLV』『KAM』『Journey Orchestration』. For 師大 EMBA CRM, 政大 ecommerce, 中山 marketing cases. Complements Asgard `biz-cac-ltv` (tactics) and `biz-customer-journey` (single method) with the strategic integration layer.".
日本語の概要は準備中です。原文の説明を表示しています。
Design data models with Pydantic schemas, comprehensive validation rules, type annotations, and relationship mappings.
日本語の概要は準備中です。原文の説明を表示しています。
Identify and exploit GraphQL API vulnerabilities by leveraging Introspection queries to dump the entire database schema, performing query batching to bypass rate limits (brute forcing), and extracting deeply nested unauthorized data via graph relationship abuse.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with SQLAlchemy 2.0 in Python - declarative models, queries, sessions, async engines, Alembic migrations, relationship loading strategies, N+1 detection, pool exhaustion, or 2.0 migration
日本語の概要は準備中です。原文の説明を表示しています。
Write effective MCP server instructions for tool compaction support. Use when creating or updating the `instructions` parameter in MaaSProtectedFastMCP server initialization. Helps LLMs understand when to search for tools, workflow patterns, and cross-feature relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Unity NPC behavior design-to-code translation. Perception system architecture, decision layer patterns, action execution pipeline, faction & relationship systems, NPC memory & forgetting, crowd & squad coordination. DESIGN INTENT format: INTENT/WRONG/RIGHT/SCAFFOLD/DESIGN HOOK. Based on Unity 6.3 LTS.
日本語の概要は準備中です。原文の説明を表示しています。
Public relations, corporate communications, and analyst relations for B2B SaaS. Use this skill for earned media and press strategy, announcements and press releases, executive and crisis communications, media relationships and briefings, and the Gartner/Forrester/IDC analyst program including Magic Quadrant and Wave evaluation submissions. Also triggers on: PR, public relations, press release, earned media, media relations, journalist, embargo, announcement, crisis comms, corporate communications, analyst relations, AR, Gartner, Forrester, IDC, Magic Quadrant, Forrester Wave, analyst briefing, inquiry, newsjacking, rapid response, should we comment on this news story, expert commentary, reactive comment, source request, Qwoted, is this newsworthy.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Credit Analyst — spreading financial statements and computing leverage/coverage ratios, writing a commercial credit memo, assigning or recommending an internal risk rating, structuring covenants on a term loan or revolver, or stress-testing a borrower's debt service under a downside case. Narrower than loan-officer (originates and manages the client relationship; the analyst underwrites the credit that officer brings in) and financial-risk-specialist (owns portfolio-level risk and concentration limits, not single-borrower underwriting).
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Cooling/Freezing Equipment Operator — calculating freezing time for a new product thickness via the thickness-squared relationship rather than assuming linear scaling, verifying freezing completion by actual core/thermal-center temperature rather than surface temperature or elapsed time, recognizing a temperature plateau as expected latent-heat removal rather than a malfunction, or matching belt speed/residence time to the calculated freezing time requirement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Concierge — securing a reservation at a fully-booked restaurant or sold-out venue, coordinating a multi-vendor guest request (dinner, transportation, and a gift delivery) inside a tight window, deciding when to pivot from a failed Plan A to a same-caliber Plan B, or navigating a paid-referral relationship without letting the commission distort the recommendation.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely means cancel the current task.
日本語の概要は準備中です。原文の説明を表示しています。
Audit pharmaceutical yield prediction systems and process analytical technology -- evaluate critical process parameter (CPP) to critical quality attribute (CQA) relationships, design space characterization per ICH Q8(R2) Quality by Design, PAT sensor readiness (NIR, Raman.
日本語の概要は準備中です。原文の説明を表示しています。