Demand Signals

v1.0.0

Identify emerging product categories and consumer demand signals from TikTok comments, search trends, and creator activity before they peak.

0· 52·0 current·0 all-time
byLeroyCreates@leooooooow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description promise a framework for evaluating TikTok-derived demand signals; the skill's instructions request exactly the kind of user-provided inputs (trend observation, product category, optional lead time) needed to perform that analysis. No unrelated capabilities or credentials are requested.
Instruction Scope
SKILL.md describes a bounded runtime behaviour: accept explicit user observations, evaluate them against a signal-framework, and produce a five-part structured output. It explicitly notes it cannot access live TikTok analytics and does not instruct reading local files, fetching external data, or contacting third-party endpoints.
Install Mechanism
There is no install spec and no code files — the skill is instruction-only, so nothing will be written to disk or pulled from external URLs. This is the lowest-risk install profile.
Credentials
The skill requires no environment variables, credentials, or config paths. That aligns with its stated purpose of analyzing user-supplied observations rather than querying protected APIs or performing authenticated scraping.
Persistence & Privilege
The skill is not forced-always, and uses the platform-default model invocation behavior. It does not request persistent system-level privileges or modifications to other skills. Autonomous invocation is allowed by default but is not combined with other concerning privileges here.
Assessment
This skill is a passive analysis framework that relies on you to paste or describe what you see; it does not fetch TikTok data or require credentials. Before installing or using it, consider: (1) do not paste any private customer data, account tokens, or supplier secrets into the inputs; (2) if you want the agent to run automated scraping or connect to TikTok in future versions, require explicit credentials and verify the install spec and data-handling details; (3) review any update that adds an install step, network calls, or requests for keys — those would materially change the security posture; and (4) if you prefer to avoid autonomous runs, change the skill invocation settings in your agent to require explicit user invocation.

Like a lobster shell, security has layers — review code before you run it.

latestvk97fm85337ne1yvyya7f3kbsnd83svtz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments