'methodology' 검색 결과

Compares PIA/DPIA methodologies: CNIL PIA tool, ICO DPIA template, NIST Privacy Framework, and ISO 29134. Provides methodology selection criteria based on regulatory jurisdiction, organisation maturity, processing complexity, and resource availability. Covers regulatory acceptance, tool features, and cross-methodology mapping. Keywords: PIA methodology, CNIL, ICO, NIST Privacy Framework, ISO 29134, DPIA comparison, assessment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Organize software development from requirements and architecture through testing, review, and deployment. Use specialized agent roles, shared memory, and test-driven development, where tests are written before code, to coordinate work across the project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan and implement a new feature
• Refactor legacy code with supporting tests
• Review code security and performance

Check or configure how an Obsidian vault organizes knowledge, then suggest destinations for new notes using Generic, LYT, PARA, or Zettelkasten. Preview configuration changes before applying them; existing notes stay in place.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check the vault's current organization method
• Configure PARA or another supported method
• Find a destination for a planned concept note

Inspect a project's code, history, tests, and documentation, then ask three focused questions to recommend an AI-assisted development approach. Receive one combination of methods, reasons for the choice, and practical first steps tailored to the project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing an AI-assisted workflow for a new project
• Reviewing development methods for an existing service
• Aligning specifications and tests across services

Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 5-stage recon pipeline (seed discovery, asset expansion, enrichment, exposure analysis, reporting), asset-graph discipline with 29 asset types, severity rubric (CRITICAL/HIGH/MEDIUM/LOW/INFO), confidence upgrade workflows, time budgeting, asset-level triage rules, scale-based tactics, identity-fabric mapping (Entra/Okta/ADFS/Google/SAML/M365 Teams+SharePoint+OAuth), API and auth-map methodology, JavaScript deep analysis, mobile attack surface, cloud attack surface, breach×identity correlation, detectability tagging, detection-aware probing (back-off, persona rotation), read-only validator discipline, WAF/CDN bypass + origin discovery, vulnerability prioritization (CVE/EPSS/KEV), phishing infrastructure planning + pretext development, bug bounty submission templates, client deliverable templates with risk translation, threat-actor investigation (incl. RU/CN pivots), cryptocurrency tracing, image/video forensics, chronolocation. Use when planning or executing reconnaissance against authorized targets, mapping an organization's external attack surface, investigating a person/entity, tracing crypto flows, geolocating media, or performing attribution work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Organization-grade identity-fabric mapping: tenant/federation fingerprinting and the pre-auth user-ENUMERATION oracle methodology — enumeration and fingerprint only, never credential submission. Covers domain-to-tenant resolution (Microsoft getuserrealm.srf Managed/Federated namespace check, Entra OIDC metadata tenant-GUID extraction, Autodiscover v2), keyless Microsoft tenant-federation mapping (GetFederationInformation SOAP -> sibling-domain discovery, discover-only ROE, FEDERATED_WITH provenance edge held out of attack-path pivoting), Okta org-slug derivation + OIDC fingerprint + governed custom-domain enumeration, ADFS passive/active fingerprint + version inference, Google Workspace MX-correlated detection, generic OIDC (Auth0/Keycloak/Ping Identity/OneLogin/Duo) discovery, SAML metadata (5 paths), Azure AD Seamless-SSO Negotiate-challenge detection, Microsoft Defender for Identity (MDI) sensor-API presence check, the user-enumeration oracle methodology for Microsoft GetCredentialType (IfExistsResult semantics: exists / doesn't-exist / exists-in-federated-tenant / throttled) and Okta /api/v1/authn (errorCode differential), Medium-detectability discipline with a hard 20-candidate-per-tenant cap and admin/role interest-based ranking, and name x confirmed-email-pattern login-candidate synthesis that FAILS CLOSED with zero output when no org pattern is confirmed. Grounded directly in a production ASM implementation's sso_idp.py, tenant_recon.py, and core/email_patterns.py modules. Deepens — does not duplicate — offensive-osint skill's Identity Fabric endpoint reference with the tenant-federation MAP, the oracle WORKFLOW, and the candidate-SYNTHESIS methodology that reference lacks. Use when fingerprinting an organization's identity provider, mapping its tenant/federation boundary, running an authorized pre-auth user-enumeration pass, or synthesizing login candidates from harvested names to feed that oracle — never for password spray, credential submission, or auth bypass.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a bounded task plan (and the agent prompt for it) that runs the 5-layer profiling methodology in .claude/skills/model-profiling/METHODOLOGY.md against one model, stops for human confirmation before any GPU work starts, then delegates the actual run to a background agent, verifies its completion claim, and routes findings into a gitignored .profiling-runs/<model>/ directory — durably tracked as a sub-issue under the tracking issue named in SKILL.md's "Result tracking" section — plus the methodology doc.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce honest product reviews and buying guides without fabricated first-hand experience, using disclosed evidence tiers: verified specs, owner-experience synthesis at scale, expert triangulation, and hands-on only when true. Use this skill whenever the user wants to write product reviews or buying guides without hands-on access, set up a review methodology, add evidence disclosure to review content, align reviews with Google's reviews system or FTC affiliate disclosure expectations, or decide when Review and Product schema are honest to use. Triggers on product review, buying guide, best-of list, review methodology, evidence basis, hands-on testing, we tested, affiliate review site, review disclosure, methodology block, original research, reviews system. Also triggers when review content claims testing that did not happen, or when an affiliate site needs a trust mechanism that survives scrutiny.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Conduct a peer review of research methodology, experimental design, and manuscript quality. Covers methodology evaluation, statistical appropriateness, reproducibility assessment, bias identification, and constructive feedback. Use when reviewing a manuscript, preprint, or internal research report, evaluating a research proposal or study protocol, assessing evidence quality behind a claim, or reviewing a thesis chapter or dissertation section.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing. This skill does not save content or migrate notes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Structured OSINT methodology framework: target definition, source selection, collection workflows, data correlation, timeline reconstruction, and reporting. Use to guide systematic OSINT campaigns or teach OSINT methodology.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 5-stage recon pipeline (seed discovery, asset expansion, enrichment, exposure analysis, reporting), asset-graph discipline with 29 asset types, severity rubric (CRITICAL/HIGH/MEDIUM/LOW/INFO), confidence upgrade workflows, time budgeting, asset-level triage rules, scale-based tactics, identity-fabric mapping (Entra/Okta/ADFS/Google/SAML/M365 Teams+SharePoint+OAuth), API and auth-map methodology, JavaScript deep analysis, mobile attack surface, cloud attack surface, breach×identity correlation, detectability tagging, detection-aware probing (back-off, persona rotation), read-only validator discipline, WAF/CDN bypass + origin discovery, vulnerability prioritization (CVE/EPSS/KEV), phishing infrastructure planning + pretext development, bug bounty submission templates, client deliverable templates with risk translation, threat-actor investigation (incl. RU/CN pivots), cryptocurrency tracing,...

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

회사의 서비스, 고객상, 차별화 근거를 바탕으로 비교할 경쟁사와 조사 출처를 고릅니다. 직접·인접 경쟁사와 목표 기업으로 분류하고 출처가 있는 후보 목록을 만듭니다.

• 자세히 비교할 경쟁사 선정
• 직접·인접 경쟁사와 목표 기업 분류
• 시장 조사 보고서의 후보 압축

점수가 매겨진 경쟁사 자료를 시장 지도, 비교표, 차별화 여지와 우선 실행안을 담은 보고서로 정리합니다. 경영진 보고와 팀의 경쟁 전략 결정에 활용합니다.

• 경영진·이사회용 경쟁 현황 보고
• 완성된 경쟁사 프로필 통합
• 차별화 여지와 경쟁 위협 검토

Turn CSV, Excel, or JSON data into a visual report page with key metrics, multiple charts, a data table, and written observations. The report uses supplied data and includes its source, reporting period, and methodology.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn growth data into a visual weekly report
• Present key metrics and year-over-year changes
• Share charts alongside source data and methodology

Organize software development from requirements and design through testing, review, and deployment. Uses Claude Flow to coordinate specialized agents, share decisions across sessions, and guide implementation with tests written before code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Developing a feature from requirements through review
• Refactoring legacy code with supporting tests
• Investigating bugs and adding regression tests