「methodology」の検索結果

Use when doing upstream market-research methodology — sizing a market as TAM/SAM/SOM computed BOTH top-down and bottoms-up (never a single unsourced number), planning a survey sample size with finite-population correction and per-segment minimums, or scoring candidate market segments against Kotler's measurable/substantial/accessible/differentiable/actionable criteria. Outputs always show the method and the assumptions. For market-research analysts and product-marketing at the sizing/survey/segmentation moment. Distinct from marketing-skill (campaign analytics, attribution, demand-gen) — this is the evidence-building methodology, not live-campaign optimization.

日本語の概要は準備中です。原文の説明を表示しています。

Measures and improves the quality of AI models and agents on Google Cloud using the Eval Quality Flywheel methodology. Use when generating synthetic user scenarios, evaluating an agent or model, building an eval dataset, picking or writing evaluation metrics, analyzing failures, comparing results before and after a fix, or when guidance is needed on Agent Platform eval methodology — including dataset schema, LLM-as-judge scoring, and common failure causes. For fine-tuning, use agent-platform-tuning. For general production deployment, use agent-platform-deploy.

日本語の概要は準備中です。原文の説明を表示しています。

External research synthesis from Trail of Bits, SlowMist, ConsenSys, Immunefi, and Cyfrin. Use this for advanced audit methodology, Echidna/Medusa fuzzing setup, Slither custom detector writing, attack pattern deep dives, or the 4-phase learning roadmap.

日本語の概要は準備中です。原文の説明を表示しています。

Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI namespace attacks through --extra-index-url resolution ordering, NuGet feed priority exploitation when multiple package sources are configured without clear directives, Maven and Gradle repository ordering where artifact resolution traverses repositories sequentially, Go module proxy abuse through GOPROXY misconfiguration, Ruby gems namespace squatting, and Docker image tag confusion with unqualified image references. Provides complete proof-of-concept methodology using safe callbacks including DNS canary via interactsh or Burp Collaborator and HTTP beacon with no destructive payload. Covers reconnaissance techniques for discovering internal package names through GitHub repository analysis, error message harvesting, JavaScript source map extraction, lock file parsing, job postings mentioning internal tools, and package manifest inspection. Directly references and builds upon Alex Birsan's seminal 2021 dependency confusion research. Each ecosystem section includes registry-specific exploitation mechanics, configuration vulnerabilities, and defensive countermeasures for engagement reporting.

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "learn ethical hacking", "understand penetration testing lifecycle", "perform reconnaissance", "conduct security scanning", "exploit vulnerabilities", or "write penetration test reports". It provides comprehensive ethical hacking methodology and techniques.

日本語の概要は準備中です。原文の説明を表示しています。

Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

日本語の概要は準備中です。原文の説明を表示しています。

Golang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (→ See `samber/cc-skills-golang@golang-benchmark` skill) or debugging workflow (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 6-stage recon pipeline (seed → asset expansion → enrichment → exposure analysis → convergence → operator-armed active validation) with connector-resilience and stage-vs-gating discipline, asset-graph discipline, severity rubric, confidence upgrade workflows, time budgeting, identity-fabric mapping, breach×identity correlation with per-person identity dossiers, detectability tagging, detection-aware probing, WAF/CDN bypass, vulnerability prioritization, phishing infrastructure planning, bug bounty submission, and client deliverable templates. Use when planning or executing reconnaissance against authorized targets, mapping an organization's external attack surface, investigating a person/entity, or producing client deliverables.

日本語の概要は準備中です。原文の説明を表示しています。

Reconnaissance and methodology playbook. Use when mapping assets, discovering endpoints, fingerprinting technology, and building a structured testing plan for a new target.

日本語の概要は準備中です。原文の説明を表示しています。

Add another file (resource) to an EXISTING dataset in a PortalJS portal — a data dictionary, methodology, or an additional data file. Turns a single-file dataset into a multi-resource one; the showcase renders a section per resource. Use when a dataset needs a second file, such as a data dictionary, methodology doc, or an additional period's data.

日本語の概要は準備中です。原文の説明を表示しています。

Cavekit specification-driven development methodology — the Hunt lifecycle (Draft → Architect → Build → Inspect → Monitor) and how to apply it. Use when starting a Cavekit project, structuring an existing codebase as kits/plans, or routing between sub-skills.

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for the UNMIK Regulation 64 Panels of the Kosovo district courts (2000–2008). Citations are verified against UNMIK/EULEX archives and legal-tools.org. Keeps the Reg. 64 Panels distinct from the Kosovo Specialist Chambers, and clarifies that Reg. 2000/64 permitted (did not impose) internationally-majority panels. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for the Special Court for Sierra Leone and its Residual Special Court. Citations are verified against rscsl.org and legal-tools.org. Covers Taylor, the AFRC/CDF/RUF cases, the child-soldier and forced-marriage holdings, the head-of-State immunity decision, and the fixed-term (no life) penalty regime. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for the Special Panels for Serious Crimes of the Dili District Court (UNTAET, 2000–2006). Citations are verified against JSMP, the UN archives and legal-tools.org. Covers the Los Palos case, the Serious Crimes Unit caseload (391 indicted; about 88 tried) and the SPSC-vs-Jakarta distinction. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for the Special Tribunal for Lebanon. Citations are verified against the STL legacy archive and legal-tools.org. Covers the Ayyash et al. case, the two contempt cases (STL-14-05 New TV/Al-Khayat and STL-14-06 Akhbar Beirut/Al-Amin), and the 2011 terrorism decision. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for the post-WWII tribunals: the IMT at Nuremberg, the twelve Nuremberg Military Tribunals, and the IMTFE at Tokyo. Citations are verified against the official records (Blue/Green Series, Pritchard-Zaide) and the digital archives (Avalon, Harvard NTP, UVA IMTFE). Guards the four classic traps (IMT vs NMT; Nuremberg vs Tokyo; Charter article numbers; majority judgment vs separate opinions, e.g. the Pal dissent). Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for the ICTY, the ICTR and the Residual Mechanism (IRMCT). Citations are verified against irmct.org, the Case Law and Unified Court Records databases, and legal-tools.org. Handles the IT/ICTR to MICT case-number transition (Karadžić, Mladić) and the protective-measures rule. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library - methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for the Kosovo Specialist Chambers and Specialist Prosecutor's Office (The Hague, applying Kosovo law). Citations are verified against scp-ks.org before use; appeal registry numbers are cited only once confirmed. Covers Thaçi et al., Mustafa, Pjetër Shala and Gucati & Haradinaj. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for the ECCC (Khmer Rouge Tribunal). Every citation is verified against eccc.gov.kh, the ECCC archive or legal-tools.org. Covers Case File numbering, the 001/002/002-01/002-02 structure, the genocide findings against the Cham and the Vietnamese, and the Internal Rules revision discipline. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Draft, adapt, and review contracts and clauses aligned with The Chancery Lane Project's methodology for reducing carbon emissions through legal agreements. Use when Claude needs to: (1) Draft new climate-aligned clauses (e.g., net zero commitments, carbon accounting, supply chain decarbonization), (2) Adapt or modify existing contracts to incorporate climate objectives, (3) Review and analyze clauses for alignment with climate goals and decarbonization strategies, (4) Provide guidance on The Chancery Lane Project's house style and drafting methodology for climate-conscious legal work.

日本語の概要は準備中です。原文の説明を表示しています。

Verification-first methodology for Section I (War Crimes) of the Court of Bosnia and Herzegovina. Citations are verified against the Court of BiH, the ICTY/IRMCT archives and OSCE. Distinguishes ICTY-referred (Rule 11 bis) cases from locally-initiated ones; covers Stanković, Janković and the Maktouf lex mitior ruling. Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills

日本語の概要は準備中です。原文の説明を表示しています。

Applies the Bullseye Framework from Traction by Gabriel Weinberg and Justin Mares. Use when choosing growth channels, testing customer acquisition strategies, or deciding where to spend marketing effort. Covers all 19 traction channels with selection methodology, testing protocol, and phase-matched channel advice. Triggers include 'how do we get customers', 'which marketing channel should we use', 'we have a product but no users', 'our growth has stalled', 'should we do content marketing or paid ads', 'how do we test traction channels', 'what channels work at our stage'. NOT for product development (use Lean Startup), not for positioning/messaging (use Obviously Awesome), not for pricing (use Monetizing Innovation), not for enterprise sales methodology (use SPIN Selling).

日本語の概要は準備中です。原文の説明を表示しています。