技能详情（站内镜像，无评论）
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 551 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：良性 · OpenClaw ：良性
Package：1kalin/afrexai-business-continuity
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：良性
OpenClaw 评估
The skill is an instruction-only Business Continuity Plan generator whose requested inputs, outputs, and behavior are coherent with its stated purpose and it does not request elevated system access or install code.
目的
Name/README/SKILL.md all describe generating BCPs/DR plans; the questions the agent will ask (revenue impact, systems, vendors, contacts, RTO/RPO) are directly relevant to producing a BCP. No unrelated credentials, binaries, or config paths are requested.
说明范围
SKILL.md instructs the agent to ask the user for business details (functions, revenue loss estimates, contact trees, vendor dependencies) and then produce a markdown document. This stays within scope for a BCP generator, but it will prompt for sensitive business data (revenue figures, staff contact info, vendor details). The instructions do not direct the agent to read local files, call unexpected external endpoints, or exfiltrate data.
安装机制
There is no install spec and no code files — instruction-only skill. Nothing is written to disk or downloaded during install, which minimizes mechanical risk.
证书
The skill requests no environment variables, credentials, or config paths. The data it asks for is content-level (business details) rather than system-level secrets, which is proportionate for its goal.
持久
always is false and the skill does not request to modify agent/system configuration. It does not ask for persistent tokens or privileges; autonomous invocation is allowed by platform default but presents no additional red flags here.
综合结论
This skill appears coherent and low-risk because it's instruction-only, but it will ask for sensitive business data (revenue impact, employee contact numbers, vendor dependencies). Before sharing sensitive details: (1) Confirm the platform's data handling and retention policy; (2) avoid pasting credentials or secrets into prompts; (3) consider using redacted or representative sample numbers for testing; (4) review and sanitize the generated BC…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Business Continuity Planner」。简介：Create detailed business continuity and disaster recovery plans by mapping crit…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/1kalin/afrexai-business-continuity/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
# Business Continuity Planner
Build a complete Business Continuity Plan (BCP) and Disaster Recovery (DR) strategy for any organization.
## What It Does
- Maps critical business functions and their dependencies
- Assigns Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO)
- Creates communication chains and escalation paths
- Generates a full BCP document ready for stakeholder sign-off
- Identifies single points of failure before they break
## How to Use
Tell the agent about your business and it will walk you through building a BCP:
```
"Create a business continuity plan for our 40-person SaaS company"
"We need a disaster recovery plan — our main systems are AWS-hosted"
"Map our critical functions and set RTOs for each"
```
## Process
### 1. Business Impact Analysis
Ask the user about:
- Core revenue-generating functions
- Customer-facing systems
- Internal operations (payroll, comms, data)
- Key vendors and third-party dependencies
For each function, determine:
- **Impact of downtime** (revenue loss per hour, contractual penalties, reputation damage)
- **RTO** — how fast must it recover? (minutes, hours, days)
- **RPO** — how much data loss is acceptable?
### 2. Risk Assessment
Identify threats across categories:
- **Technology**: server failure, cyberattack, data corruption, cloud outage
- **People**: key person risk, mass absence, skills gap
- **Facilities**: office access, power, connectivity
- **Supply chain**: vendor failure, payment disruption
- **External**: regulatory change, natural disaster, pandemic
Rate each: Likelihood (1-5) × Impact (1-5) = Risk Score
### 3. Recovery Strategies
For each critical function, define:
- Primary recovery method
- Backup/alternative approach
- Manual workaround (if systems are down)
- Responsible person + backup person
- Dependencies that must recover first
### 4. Communication Plan
Build a contact tree:
- Crisis management team (names, roles, phone numbers)
- Escalation triggers (what constitutes a crisis?)
- Internal notification sequence
- External stakeholder communication (clients, vendors, regulators)
- Media/PR response template
### 5. BCP Document Output
Generate a structured document with:
```markdown
# Business Continuity Plan — [Company Name]
## Version: 1.0 | Last Updated: [Date] | Next Review: [Date + 6 months]
### 1. Purpose & Scope
### 2. Business Impact Analysis (table)
### 3. Risk Register (table with scores)
### 4. Recovery Strategies (per function)
### 5. Communication Plan & Contact Tree
### 6. IT Disaster Recovery Procedures
### 7. Testing Schedule (tabletop exercises quarterly, full test annually)
### 8. Document Control & Review Cycle
```
### 6. Testing & Maintenance
Recommend:
- **Tabletop exercise** quarterly — walk through a scenario verbally
- **Simulation test** bi-annually — actually invoke recovery procedures
- **Full DR test** annually — failover to backup systems
- **Review trigger**: after any real incident, org change, or new system deployment
## Output Format
Deliver the BCP as a single markdown document the user can save, print, or convert to PDF. Include tables for the Business Impact Analysis and Risk Register.
## Tips
- Start with the functions that make money. Everything else is secondary.
- A plan that exists but hasn't been tested is just a document, not a plan.
- The #1 cause of extended outages isn't technical failure — it's nobody knowing who to call.
- Keep it practical. A 5-page plan people actually read beats a 50-page plan nobody opens.