Topic Selection Expert
Analysis
The skill mostly matches its topic-monitoring purpose, but it uses Feishu account credentials to write records and can run persistently/push messages even though those authorities are not declared in the registry metadata.
Findings (4)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
url = f"{FEISHU_API}/bitable/v1/apps/{APP_TOKEN}/tables/{TABLE_ID}/records/batch_create" ... httpx.post(url, headers=headers, json={"records": batch}, timeout=30)The pipeline batch-creates Feishu records for scored topics. This matches the stated workflow, but it is an automated mutation of an external account.
nohup python3 -u main.py --daemon >> "$LOG_FILE" 2>&1 & echo $! > "$PID_FILE"
The start script launches a background daemon and records a PID. This is disclosed and paired with stop/status scripts, but it is persistent behavior.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
FEISHU_APP_SECRET = _env("FEISHU_APP_SECRET") ... APP_TOKEN = _env("FEISHU_APP_TOKEN") ... TABLE_ID = _env("FEISHU_TABLE_ID")The code requires Feishu app credentials and table identifiers, while the registry metadata declares no required env vars or primary credential. This is delegated account authority that should be surfaced clearly.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
记录用户的采纳/放弃偏好,持续优化推荐
The skill says it records accept/abandon preferences to improve future recommendations, creating persistent recommendation state.
