yotta-present@0.7.3
CAUTIONPublisher claims: "元呈 —— AI 输出的默认呈现层:智能体先把输出内容判为「内容类型」,再选「呈现形态」(结论卡/表格/正文/指标板/问答卡/报告/图表…),用 yotta_present CLI 或 present_result MCP 统一渲染成可复制的 Markdown / 纯文本(按需附本地 SVG)。平台自适应(--platform / platform):webchat 完整 Markdown、discord/whatsapp 表格转列表+标题转加粗、plain 去符号;渲染通道(--channel / channel):auto 按 platform 映射 plain→r0 去 emoji、其余→r1 emoji 徽章+引用条(r0 保底无色 / r1 增强),r3 = SVG 整卡(开源 demo:conclusion/metrics/table 三形态 + release/weekly/compare/risk 四场景模板 + 品牌 token,可编辑 SVG),r2 高级美化未开放;命名场景模板(vuln_report/faq/status,references/templates.json 可热更新)一次定义多处复用;codeblock + bold_keys 加粗 + max_len 长度熔断。触发:默认——凡交付给用户的 AI 输出都经元呈(判型 → 选形态 → 渲染)呈现;例外见正文白名单。边界:不做交互式图表编辑器 / BI / 数据分析工具;图表与整卡只是呈现形态之一;不做内容改写 / 判断本身。AI 首次使用自动接入 yotta-present MCP(写 mcpServers + 永久记忆护栏,均需用户明确同意),输出默认统一呈现、未加载时降级 CLI。" Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 63/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
17 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim yottameta: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.