Sql To Doc

执行SQL查询并将结果按照指定模板整理后写入飞书云文档。适用于数据周报、数据汇总、统计报告等场景。

This skill looks plausible for automating DataWorks→Feishu reports, but there are inconsistencies you should resolve before installing or granting credentials: - Ask the publisher why no Feishu credentials are declared. Creating Feishu docs and sending IMs normally requires Feishu app tokens (APP_ID/APP_SECRET or API token). Do not provide broad Feishu or platform tokens until you confirm exact required scopes. - Confirm what META_CENTER_TOKEN grants. Limit tokens to least privilege (only access to the specific DataWorks project and read-only SQL execution if possible). - Request details about the 'feishu_create_doc' and 'feishu_im_user_message' helpers: are they platform-provided, audited internal actions, or custom scripts? Prefer well-known, documented integration points. - Because the skill uses exec to call DataWorks OpenAPI, test it first in a safe environment (non-production project) to confirm it only runs intended queries. - Prefer a published source or homepage and a verifiable owner. The package has unknown source — that raises supply-chain risk. If the publisher provides the missing credential requirements, limited-scope tokens, and a clear explanation of the helper tools, the skill would be more coherent. Until then treat it with caution and avoid exposing high-privilege credentials.

Type: OpenClaw Skill Name: sql-to-doc Version: 1.0.0 The sql-to-doc skill (SKILL.md) enables arbitrary SQL execution on MaxCompute and Jinja2 template rendering to automate Feishu document creation. These are high-risk capabilities that introduce potential for SQL injection and Server-Side Template Injection (SSTI), though they appear aligned with the stated purpose. No evidence of intentional malice, unauthorized data exfiltration, or prompt injection was found.