← Back to Skills Marketplace
fffdz

Survival Manager

by tianyi · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
320
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install survival-manager
Description
自主调整运行模式,管理资金与任务,需用户授权高风险操作,保障系统稳定与财务健康的生存管理工具。
Usage Guidance
This skill is plausible for local financial/agent management but has a few unclear points you should verify before installing: - Telegram & notifications: SKILL.md mentions Telegram notifications but the skill does not declare or request any Telegram API token or explain how the 'message' tool is configured. Ask the author how notifications are delivered and where credentials are stored; do not provide tokens unless you trust the integration. - Model invocation & costs: The skill references qwen3.5-* models and per-call costs. Confirm whether model calls go through your OpenClaw account (and billing) or require external API keys. Understand and accept potential usage costs before enabling autonomous behavior. - File writes and authorization flow: The scripts will write and update local files (finance logs, survival-config.json, authorization-pending.md). Ensure these files and their paths are acceptable and that the authorization flow actually pauses high-risk operations the way you expect. - OS mismatch: Provided scripts are PowerShell (.ps1) but the skill has no OS restriction. If you run on non-Windows hosts, verify compatibility or convert scripts. - Test in a sandbox: Run the skill in an isolated environment first to confirm where network calls go, what files are created/modified, and how notifications are sent. Inspect survival-config.json and scripts line-by-line. If the author can clarify how Telegram and model invocations are configured (what credentials are needed and where they are stored), and if you confirm the skill will not receive or require hidden secrets, the inconsistencies become minor. Without that clarification, proceed cautiously.
Capability Analysis
Type: OpenClaw Skill Name: survival-manager Version: 1.0.0 The skill is designed for local agent management, focusing on financial tracking and operational adjustments based on a 'survival level' system. It explicitly states '无外部 API 调用' (No external API calls) and '无数据离开机器' (No data leaves the machine) in SKILL.md, and its PowerShell scripts perform only local file operations (reading/writing JSON/Markdown files). High-risk actions like file writes and sending external messages are clearly documented as requiring user authorization, indicating a design focused on transparency and user control rather than malicious intent. There are no signs of data exfiltration, obfuscation, or prompt injection attempts to bypass security measures.
Capability Assessment
Purpose & Capability
The skill's name and description (manage funds, heartbeats, authorization queue) align with the provided instructions and PowerShell scripts: balance checks, logging income/expenses, authorization flow, and subagent coordination. However, SKILL.md asserts 'no external endpoints' while also describing Telegram notifications and invoking external models (qwen3.5 variants) via OpenClaw—these require external connectivity/credentials or platform-level services and are not declared. Additionally, all runtime scripts are PowerShell (Windows-oriented) but the skill metadata has no OS restriction—an operational mismatch.
Instruction Scope
Instructions stay mostly within the declared scope: local file reads/writes (with writes requiring authorization), periodic checks, and creating authorization requests. The doc also allows network searches, browser snapshots, and model invocations; those are described as optional or platform-provided, but the skill instructs sending Telegram notifications via a 'message tool' without showing how that tool is configured. The authorization flow and file paths are explicit, which is good; the vague references to external notifications and model calls grant the agent broader runtime capabilities unless the host constrains them.
Install Mechanism
Instruction-only skill with no install spec and no code files beyond plain PowerShell scripts and markdown. No downloads or archive extraction are present, which lowers installation risk.
Credentials
The skill declares no required environment variables or credentials, yet it references Telegram notifications and external model invocation (qwen3.5-*). Those integrations typically require API keys or platform-managed credentials. The absence of declared env vars or guidance for configuring notification credentials is an inconsistency that could hide required secrets or rely on implicit platform plumbing.
Persistence & Privilege
always:false (normal). Skill does not request to force-enable itself or change other skills. It writes to its own local files (authorization-pending.md, finance logs, survival-config.json) when authorized—this is expected for its purpose.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install survival-manager
  3. After installation, invoke the skill by name or use /survival-manager
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Slug survival-manager
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Survival Manager?

自主调整运行模式,管理资金与任务,需用户授权高风险操作,保障系统稳定与财务健康的生存管理工具。 It is an AI Agent Skill for Claude Code / OpenClaw, with 320 downloads so far.

How do I install Survival Manager?

Run "/install survival-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Survival Manager free?

Yes, Survival Manager is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Survival Manager support?

Survival Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Survival Manager?

It is built and maintained by tianyi (@fffdz); the current version is v1.0.0.

💬 Comments