Financial Design Systems
v1.0.0Patterns for building dark-themed financial charts and data visualizations. Covers chart theming, color scales for gains/losses, and real-time data display. Use when building trading dashboards or financial analytics. Triggers on chart theme, data visualization, financial chart, dark theme, gains losses, trading UI.
⭐ 0· 1.1k·3 current·3 all-time
by@wpank
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the contents: the SKILL.md contains UI code snippets, color palettes, and chart components appropriate for a financial design-systems skill. There are no unrelated environment variables, binaries, or capabilities requested.
Instruction Scope
The runtime instructions are just design patterns and example components (Recharts, lightweight-charts, SVG sparklines). They do not direct the agent to read local secrets, system files, or send data to external endpoints. No vague 'gather any context' language was found.
Install Mechanism
The registry entry has no install spec (lowest risk). The README includes example installation commands (an 'npx add' with a GitHub tree URL and instructions copying from ~/.ai-skills or ~/.cursor), which are not part of the skill registry install spec and should be treated as documentation only. Advisable to verify and prefer cloning or installing from an official repo rather than blindly running npx commands that reference arbitrary URLs.
Credentials
No environment variables, credentials, or config paths are required. The skill does not request secret tokens or unrelated credentials.
Persistence & Privilege
always is false and the skill does not request persistent/privileged installation. It is user-invocable and may be invoked autonomously (platform default), which is expected for a skill of this type.
Assessment
This skill appears coherent and focused on UI patterns for financial charts. Before installing or executing any of the README's shell commands: (1) verify the source repository and review the full code for any network calls or unexpected behavior, (2) avoid blindly running arbitrary npx commands pointing at unfamiliar URLs—prefer cloning the official repo or installing from a trusted package source, (3) inspect any copied files for scripts that might access local paths, and (4) confirm license and provenance if you plan to include the code in production. Autonomous invocation is normal, but you should still review the skill's content before granting it run-time use in automated workflows.Like a lobster shell, security has layers — review code before you run it.
latestvk975y805zmhbb0ky1pq83b5k0n80wfq7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.