'methodology' 검색 결과

Redact reverse-engineering findings for public disclosure while preserving methodology, generalizable patterns, and teaching value. Covers the private-vs-public repo split, deny-list pattern maintenance, orphan-commit publish pattern that prevents `git log` leaks, category-based redaction calibration (methodology/pattern/version-finding/internal), and the `check-redaction.sh`-style CI gate that blocks merges when a deny-listed pattern appears. Use when publishing findings about a CLI harness you don't own, when preparing upstream proposals to an unrelated project, or when archiving a private research repo for public reference.

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

Systematic methodology for achieving 100% backward dataflow reachability in a new language. Create gauntlet fixture, write trace, diagnose gaps, fix analyzer/algorithm, iterate to 100%. Language-agnostic process. Use when: (1) adding a new language to Grafema, (2) auditing dataflow coverage for existing language, (3) user says "/dataflow-gauntlet".

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

Structured OSINT collection methodology. Planning, collection techniques, search operators, and documentation. Loaded by the osint-researcher agent.

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

Investigation flow (Glob -> Grep -> Read), evidence-based research with file:line references, structured output format for AI consumption. Use for pattern discovery, implementation research, and codebase investigation.

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

Post-mortem analysis of a PhysicsIntern workspace run (Claude Code, Pi, Codex, or OpenCode host). Reconstructs the trajectory from the session record — JSONL file(s) for Claude/Pi/Codex, the SQLite store for OpenCode — audits methodology adherence against the workspace's own CLAUDE.md / AGENTS.md and skill/agent prompts, checks commit discipline and flag dispositions, and assesses substantive quality. Produces a thorough evidence-anchored markdown report. Use after a workspace has been worked on to identify what went well, where the methodology slipped, and what prompts to improve.

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

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

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

Consult this skill BEFORE proposing a fix to any CLI gap or schema gap that touches evidence, trust magnitude, evidence types, evidence grades, the TM formula, or star-level promotion gates. Also read it whenever an issue mentions citations, stars, commits, contributors, views, reviewers, percentile, arxiv, github-stars-own, repo-own, social-signal, benchmark-result, peer-review, self-attestation, fusion-recipe, verifier-attestation, or proxy-containment — those are the 10 canonical evidence types and the raw inputs that feed their formulas. Also read it when asked whether a skill qualifies for a given star level (0★–6★): the Star Bar and promotion gates live in `META.md`, not in the TM methodology page. Reading both prevents proposing a calibration that satisfies the TM grade threshold but violates a Star Bar installability or link requirement.

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

Measures and improves the quality of AI models and agents on Google Cloud using the Eval Quality Flywheel methodology. Use when 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.

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

Eliciting and documenting a sales process before it is built in Salesforce: stage sequencing, entry/exit criteria per stage, win/loss analysis requirements, and stage transition rules. Trigger keywords: sales process design, stage discovery, entry criteria, exit criteria, stage gate, win/loss categorisation, sales methodology, pipeline stages, opportunity stage mapping, stage ladder, probability ladder, forecast category mapping, required fields per stage, stage swim lane, discovery workshop, handoff brief. NOT for configuring OpportunityStage, Sales Processes or Path in Setup — use admin/opportunity-management. NOT for cross-functional swim-lane maps — use admin/process-flow-as-is-to-be.

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

Use for ab methodology recipes when optimizing a Coworld player.

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

Use for Crewrift-specific ab methodology recipes when optimizing a player.

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

Use for ab methodology recipes in scripted Coworld policy optimization.

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

Use for reusable ab methodology recipes in software and coding-agent work.

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

Application of Six Sigma quality methodology to AI agent process improvement and reliability

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

GOMS cognitive modeling methodology for analyzing human-computer interaction task performance

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

Cognitive Systems Engineering design methodology for joint cognitive systems and human-centered automation

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

Methodology for eliciting expert knowledge about cognitive processes, decisions, and mental models in complex tasks

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

Integration of BDI agent architecture with soft systems methodology for complex organizational problem-solving

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

Systematic methodology for eliciting, representing, and operationalizing expert cognitive skills—pattern recognition, situation assessment, mental simulation—from practitioners without requiring research training. Bridges academic rigor and practical usability.

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

Core statistical methodology and pedagogical approach for all Inquiro analyses. Always loaded to maintain teaching quality and reproducibility standards.

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

KPI体系設計とOKR策定支援スキル。ビジネス目標に整合したKPI設計、バランススコアカード、OKRフレームワーク、 ダッシュボード設計を提供。SMART原則、リーディング/ラギング指標の選定を支援。 Use when designing KPI frameworks, implementing OKR methodology, or creating performance measurement systems. Triggers: "KPI design", "OKR", "performance metrics", "balanced scorecard", "dashboard design", "measurement framework".

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

Conduct a defensible cybersecurity risk assessment using the NIST SP 800-30 Rev 1 methodology: prepare scope and a risk model, identify threat sources and threat events, identify vulnerabilities and predisposing conditions, determine likelihood and impact, compute risk, and communicate results as a prioritized risk register. Use when an organization needs an actual risk *assessment* (not a maturity score), when a control framework (CSF, ISO 27001, RMF, SOC 2, PCI) requires a documented risk analysis as input, when leadership asks "what are our top risks and how bad are they", when assessing risk for a new system or major change, or when building a risk register from scratch. This is the methodology that feeds framework selection, ATO packages, and treatment decisions. Keywords: risk assessment, NIST 800-30, threat modeling, likelihood and impact, risk register, risk analysis, threat sources, vulnerabilities, risk determination, qualitative risk, risk matrix, residual risk, risk treatment.

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

Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when an organization handles Controlled Unclassified Information (CUI) under a DoD contract, when a contract carries DFARS clause 252.204-7012/7019/7020/7021, when preparing for or responding to a CMMC assessment, when computing or improving an SPRS score, when building a System Security Plan or POA&M for 800-171, or when scoping which systems are in the CUI boundary. Keywords: CMMC, CMMC Level 2, NIST 800-171, SP 800-171 Rev 2, CUI, FCI, SPRS, DFARS 7012, C3PAO, POA&M, System Security Plan, DoD Assessment Methodology, 110 controls, defense industrial base, DIB, FedRAMP equivalency.

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

This skill should be used when the user asks to "follow red team methodology", "perform bug bounty hunting", "automate reconnaissance", "hunt for XSS vulnerabilities", "enumerate subdomains", or needs security researcher techniques and tool configurations from top bug bounty hunters.

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