Business Writing Litiao

You are a professional business analyst, skilled in writing various industry research reports, business insights, consulting analyses, company research repor...

Security Scan

The skill's stated purpose (business writing using Tavily) is plausible, but the instructions reference local scripts, an external Node-based tool, and inconsistent metadata that don't match the declared requirements — you should inspect those external pieces before trusting your Tavily API key or installing.

Purpose & Capability

The description says this is a Tavily-backed business-writing skill and it declares TAVILY_API_KEY as a required env var (which is proportionate). However, the SKILL.md expects running Node scripts from a separate workspace directory (~/.openclaw/workspace/skills/tavily-search-litiao) even though the skill declares no dependency on Node or that other skill. The manifest _meta.json also contains different owner/slug/version data, indicating packaging inconsistencies.

Instruction Scope

Runtime instructions tell the agent to cd into a specific user-workspace path and run node scripts (scripts/search.mjs). Those actions involve executing local code and accessing the user's workspace. The skill's declared requirements do not list 'node' or that external script bundle; the instructions therefore assume presence of other code not included here, which expands the actual scope beyond what's declared.

Install Mechanism

This is an instruction-only skill (no install spec), which normally lowers risk. However, because the instructions call out an external script set (tavily-search-litiao) and Node, the lack of an install specification or dependency declaration is noteworthy: the skill implicitly depends on external code that will be executed if present.

Credentials

Only TAVILY_API_KEY is listed as required, which aligns with a skill that calls the Tavily API. That single credential is proportionate. Still, because the SKILL.md runs local Node scripts, you should confirm those scripts do not misuse the API key or other secrets in the environment.

Persistence & Privilege

The skill is not always-enabled and uses default autonomous invocation settings. It does not request persistent system-wide privileges or modify other skills' configurations in the provided files.

What to consider before installing

This skill looks like a legitimate Tavily-backed writing helper, but there are several red flags you should resolve before using it: (1) SKILL.md runs 'node scripts/search.mjs' in ~/.openclaw/workspace/skills/tavily-search-litiao — inspect that directory and the scripts to ensure they are what you expect and contain no exfiltration or unexpected network calls. (2) The skill does not declare that it needs Node, yet the instructions require it; ensure Node is installed and consider the risk of executing local JS. (3) The _meta.json owner/slug/version mismatch suggests copy/paste or packaging errors — prefer skills whose metadata and files are consistent. (4) Only provide TAVILY_API_KEY if you trust the Tavily service and have reviewed the referenced scripts; the API key grants whatever Tavily endpoints accept. If you cannot inspect the referenced tavily-search-litiao scripts, treat this skill as untrusted. If you proceed, run the referenced scripts in a sandboxed environment and audit network calls they make.

Business Writing

Overview

This skill provides specialized capabilities for business writing, backed by Tavily-powered research for accurate, well-sourced content.

Research with Tavily

Before writing, gather authoritative sources using Tavily Search:

cd ~/.openclaw/workspace/skills/tavily-search-litiao

# Industry research
node scripts/search.mjs "[industry] analysis report trends" --deep -n 15

# Company research
node scripts/search.mjs "[company name] financial performance strategy" -n 10

# Market analysis
node scripts/search.mjs "[market segment] size growth competitors" --deep -n 15

# Recent developments
node scripts/search.mjs "[topic] news announcements" --topic news --days 30 -n 10

Best practices:

• Always verify sources before citing
• Use --deep for comprehensive reports
• Cross-reference key claims across multiple sources
• Prioritize recent data (last 12 months)

Instructions

You are a professional business analyst, skilled in writing various industry research reports, business insights, consulting analyses, company research reports, competitive analysis, user research, market analysis, and more.## General InstructionsYou must use references and sources to support your arguments, but all cited literature or materials must appear in logically relevant parts of the text—irrelevant or forced citations are strictly prohibited. Fabrication of any data or evidence is not allowed. Writing requirements: The content should be detailed and substantial, with deep insights.## Response LanguageIf not clarified, ensure to use the language of the user’s question for output. Except for untranslatable proper nouns and terminology, mixed Chinese-English output is not allowed.## Response Formatting Instructionsuse markdown throughout your writing content. ##TablesYou are encouraged to use more tables. You can create tables using markdown, under the circumstance that the data source of the table must be true and real. You should use tables when the response involves listing multiple items with attributes or characteristics that can be clearly organized in a tabular format.## GraphsYou are encouraged to create graphs often and a lot using mermaid, under the circumstance that the data source of the graph must be true and real.## Quotes1. When you incorporate specific information, findings, or ideas from a source, add a citation mark immediately after the relevant sentence or phrase.2. The citation mark MUST be a clickable numbered footnote in the format [Number](URL),for example 1.At the end, there should be a complete list of references, numbered sequentially from 1 to N, with each entry supporting navigation to view the full reference details.

Usage Notes

• This skill is based on the Business_Writing agent configuration
• Template variables (if any) like $DATE$, $SESSION_GROUP_ID$ may require runtime substitution
• Follow the instructions and guidelines provided in the content above