ClawHub

orbcafe-graph-detail-ai

v1.0.0

Build ORBCAFE graph analytics dialogs, detail pages, and AI settings flows using CGraphReport, chart components, CDetailInfoPage/useDetailInfo, and CCustomiz...

⭐ 0· 182·0 current·0 all-time
by@shenruiyang
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/description (graph dialogs, detail pages, AI settings) aligns with the SKILL.md recipes and references. The skill does not request unrelated credentials or binaries, and all required behaviours are UI-focused and consistent with building ORBCAFE components.
✓
Instruction Scope
Runtime instructions are constrained: pick domain, load a minimal recipe, apply guardrails, and return a small code snippet + data model. The SKILL.md does not instruct reading system files, environment secrets, or sending data to unexpected external endpoints.
✓
Install Mechanism
No install spec and no code files that would be written/executed — instruction-only skills present the lowest install risk. Nothing is downloaded or extracted.
ℹ
Credentials
The skill requests no environment variables or credentials (proportionate). Note: the recipes and CCustomizeAgent examples mention an apiKey/baseUrl for LLM integration; that is appropriate for a UI settings flow, but any implementation that persists or transmits API keys should handle them securely (server-side storage, not client logs).
✓
Persistence & Privilege
always is false and the skill is user-invocable only. It does not request persistent system-wide configuration changes or other skills' credentials.
Assessment
This skill is an instruction-only UI helper and appears internally consistent. Before installing or using it, verify that: (1) any code you implement from its snippets persists LLM API keys and settings securely on the server side (do not expose keys in client logs or public debug panels), (2) any baseUrl used points to your organization's LLM endpoint (the recipe shows '/llm-api' as an example), and (3) you audit any real implementation that wires onSaveAll to storage to ensure keys/templates are saved atomically and not leaked. Because the skill is instruction-only, the real security posture depends on how you implement the saved settings and LLM integrations.

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

latestvk97141gyh2na5thxqza9q55r1s82p72y

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments