'playbooks' 검색 결과

Use this skill when a company has no incident response plan, has one copied from a template that names teams it does not have, or an auditor, customer or insurer asks for it, and the team says "write our incident response plan", "IR plan", "security incident procedure", "who does what in an incident", "incident playbooks", "contact tree for incidents" or "our plan failed in the last incident". Drafts a plan sized to the company with roles and deputies, a severity scale, a contact tree with an out-of-band channel, one-page playbooks for the likely scenarios, evidence handling and a notification decision step, plus a one-page quick reference card.

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

List all pb-* playbooks with duration, difficulty and requirements, and start one. Generated from plugin-commands.json; invoke as $bdb-aos:playbooks.

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

Design a self-improvement loop for a shipped product's AI agents — production traces feed evals, evals feed improvement proposals (prompts, playbooks, retrieval configs), and a human approval gate promotes changes with rollback. Technique-agnostic: chooses per project between ACE-style evolving playbooks, GEPA/MIPROv2 offline optimization, or simple eval-driven iteration via references/techniques.md. Load when the user asks to make my product's agents self-improving, learn from production traces, add a learning loop, evolve prompts or playbooks safely, promote agent improvements, or GEPA-style optimization. NOT harness-evolution (that improves the coding agent), NOT experimentation (product A/B tests), NOT agent-run-retro (dev-phase manual retros — this skill is the production-scale continuation).

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

Create reusable procedures for responding to security incidents, from detection and containment to recovery. Define decision points, responsibilities, escalation rules, and workflows for security automation platforms so teams can follow a consistent response process.

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

• Establishing an incident response program
• Documenting phishing or ransomware response procedures
• Designing automated security response workflows

Open-source growth playbooks for AI products, B2B SaaS, and developer tools. Covers Product Hunt launch, GitHub star growth, KOL/UGC strategy, ASO, and community building. MIT licensed.

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

Index and shared harness for the 19 signal playbooks. Each playbook turns one buying signal (new in role, raised a round, hiring surge, pricing page, tech on website, ...) into one copy-ready sentence you can drop into a cold email. Every playbook ships three ways to run it: as a Claude skill, as a Clay table built through a browser harness, and as a Clay workflow built from the clay CLI. Use when someone says "personalize this list", "what signal should I use", "build the Clay column for X", or names any of the 19 signals.

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

The original reddapi.dev Reddit search skill (vector search, semantic search, trends, subreddit discovery), no Reddit OAuth or app registration needed. This is the same engine now packaged as reddit-research with added market-research playbooks and a fuller pitch on semantic vs keyword search; reddapi is kept live under its original name for existing installs and works standalone. Use when the user says 'reddapi' by name, or wants a minimal drop-in Reddit search skill without the extra research-workflow guidance. For the expanded research-oriented version with query playbooks, see reddit-research. For B2B lead scoring, see reddit-leads. For a bare API reference, see reddit-search-api.

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

Update docs, playbooks, shims, generated docs, and alignment checks so public instructions route to the right canonical sources.

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

Knowledge base from NIST SP 800-61 Rev. 3 (Incident Response Recommendations for Cybersecurity Risk Management). Use for CSF 2.0-aligned incident response life cycles, IR roles, Community Profile priorities for DE/RS/RC and preparation, playbooks, coordination, and continuous improvement. Covers 800-61r3 only; does not replace CSF 2.0 full text, SP 800-61r2 tactical playbooks, or sector-specific breach-notification law.

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

Expert en Ansible (playbooks, roles, inventory, Galaxy, configuration idempotente)

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

MCP와 외부 서비스 연동을 조사하고 근거를 갖춘 계획을 PR로 정리합니다. 사람이 특정 조사 버전과 연결 범위를 승인하면 Paperclip에서 연결별로 구현하고 검증합니다.

• MCP와 외부 서비스의 연결 요건 조사
• 사람의 승인을 받을 연동 계획 작성
• 승인된 Paperclip 연결을 개별 구현

Paperclip에서 Ramp의 최신 공식 절차를 가져와 계좌 신청, 카드 발급, 송금 등을 승인 범위 안에서 진행하고, 작업 결과와 승인 대기 사항을 기록합니다.

• Ramp 계좌 신청에 필요한 승인 준비
• 승인을 받아 에이전트용 카드 설정
• 지출과 결제 승인 절차 진행

Develop incident response procedures for LLM outages, declining answer quality, spending spikes, and unsafe outputs. Use example monitoring alerts, severity levels, recovery playbooks, and postmortem guidance to organize detection, response, and follow-up work.

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

• Plan fallback procedures for model provider outages
• Investigate declining answer quality after a deployment
• Prepare emergency controls for token spending spikes

Turn Airflow Improvement Proposals into practical guides checked against current code, or proposed user stories for design review before implementation. Organize use cases, distinguish verified examples from speculative code, and capture specific design questions.

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

• Create implementation-backed guides for an Airflow proposal
• Explore user stories before a feature is implemented
• Separate implemented features from proposed functionality

Plan a new product launch around finding early customers, guiding their first use, and running short experiments. The skill also helps diagnose stalled adoption, document repeatable outreach methods, and assess whether customer demand supports further expansion.

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

• Finding the first customers for a new product
• Diagnosing weak adoption after launch
• Planning two-week experiments

Build automated responses to AWS GuardDuty security findings using EventBridge and Lambda. Configure severity filters, isolate EC2 instances, disable compromised access keys, preserve disk snapshots for investigation, and send notifications to security teams.

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

• Triggering responses to high-severity GuardDuty findings
• Isolating EC2 instances and preserving investigation data
• Disabling compromised IAM access keys

Set up and operate Amazon GuardDuty to detect threats in AWS. Configure protection features, centralize findings across accounts, investigate suspicious activity, and build automated responses with EventBridge and Lambda, including containment of potentially compromised resources.

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

• Setting up threat detection for AWS accounts
• Investigating credential abuse and compromised instances
• Automating responses to high-severity findings

Guide a structured review after a security incident, using timelines and response data to identify root causes and process gaps. Produce review notes, response metrics, and practical improvements with named owners and deadlines.

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

• Reviewing response after a ransomware incident
• Turning exercise findings into process improvements
• Updating incident response playbooks

Set up Microsoft Sentinel to collect security logs from AWS, Azure, and GCP. Build detection queries, investigate historical activity, and create automated response workflows for a centralized security operations team.

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

• Centralizing security monitoring across multiple clouds
• Migrating from an existing SIEM platform
• Automating responses to suspicious cloud activity

Create automated workflows that add threat intelligence to suspicious IP addresses, domains, URLs, and file hashes. Combine findings from multiple services into consistent alert context and confidence scores to support analysts reviewing security alerts.

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

• Adding threat context to security alerts
• Processing indicators from phishing email submissions
• Standardizing bulk indicator lookups from threat feeds

Helps B2B SaaS teams define target customers, explain product value, and plan market launches. Includes positioning frameworks, competitor comparison sheets for sales, win/loss analysis, and guidance for international expansion.

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

• Define ideal customers and buyer roles
• Clarify product positioning and messaging
• Prepare competitor comparison sheets for sales

Structure executive decisions, compare business scenarios, and prepare board or investor communications. Provides strategy and financial analysis scripts, decision checklists, and templates for organizing company priorities, leadership routines, and organizational culture initiatives.

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

• Develop a strategy and prioritize initiatives
• Compare financial scenarios for business plans
• Prepare board materials and investor updates

Plan customer acquisition through paid ads, SEO, and partnerships for growing B2B SaaS startups. Includes campaign templates, customer acquisition cost calculations, and HubSpot tracking guidance to connect marketing activity with sales opportunities.

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

• Planning campaigns across ads, SEO, and partnerships
• Reviewing ad budgets and customer acquisition costs
• Designing campaign tracking in HubSpot

Define a product’s target customers and distinctive value, then turn that positioning into market-entry plans, competitor comparison guides, launch plans, and sales materials. Includes workflows for customer validation and adapting messaging for international markets.

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

• Defining target customers and product value
• Preparing competitor comparison guides for sales
• Planning product launches and market entry