bossskill
PassAudited by ClawScan on May 12, 2026.
Overview
This appears to be a disclosed business-coaching and CRM-style assistant that stores local records and uses a licensed cloud service, with no artifact-backed hidden exfiltration or destructive behavior found.
Before installing, be comfortable with a local SQLite business-memory database and optional vendor cloud calls for paid features. Avoid storing passwords, payment data, or unnecessary sensitive personal information, and protect the local database and license cache files.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
When you ask it to record, query, export, or activate licensing, it may run the included Python command rather than just chat.
The skill documents local command execution and an approval-minimization strategy. It is purpose-aligned and constrained to explicit user triggers, but users should be aware that record/query/export/license requests can invoke local scripts.
BossSkill 要尽量减少 Hermes/OpenClaw 的 approve 弹窗...只有用户明确要求“记录、查询、生成、更新、导出、激活授权、查看简报、查找人脉、创建任务”时，才调用本地命令。
Only ask it to run record/export/license actions when you intend local changes or cloud license checks, and review command prompts if the platform shows them.
Your license key and a hashed device identifier are used for activation and may be stored in a local cache file.
License activation sends a license key and device identifier to the configured license server and caches the license key locally. This is expected for licensed features but is credential-like handling.
"license_key": license_key.strip(), "machine_id": machine_id(), "feature_name": "activate" ... result["license_key"] = license_key.strip(); write_cache(db_path, result)
Use only the official server/source, do not share the license cache file, and delete the cache if you no longer want the device linked.
Advanced paid features require trusting the vendor’s remote service, not just the local files in this package.
Some licensed capabilities depend on proprietary remote code that is not included for review. The artifact discloses this, so it is a trust/provenance note rather than evidence of malicious behavior.
Commercial core logic is hosted on the vendor server and is not included in this client package.
Use licensed cloud features only if you trust the publisher and are comfortable sending the disclosed command inputs to the vendor service.
Business contacts, customer follow-ups, employee notes, and tasks may remain in a local SQLite database and influence later advice.
The local database is designed to persist customer, team, contact, and task records for future retrieval and recommendations. This is central to the skill but can contain sensitive business information.
CREATE TABLE IF NOT EXISTS team_members ... customers ... contacts ... tasks
Avoid entering unnecessary secrets, use separate databases for separate companies/projects, and manage backups, exports, and deletion carefully.
If you use paid cloud features, the current command text and related parameters may be sent to the vendor service.
Licensed cloud-core calls send the command arguments, license key, and device identifier to the vendor endpoint. The payload is bounded and explicitly marks no local database upload, matching the privacy documentation.
"command": command, "args": {...}, "license_key": read_license_key(db_path), "machine_id": machine_id(), "privacy_mode": "no_local_database_upload"Do not include unnecessary confidential customer, employee, financial, or legal details in cloud-feature prompts unless you are comfortable sharing them with the vendor.