fronius

Solid

Read Fronius photovoltaic inverter data through the local Fronius Solar API V1 or Solar.web Query API cloud, without exposing access-key material.

AI & Automation 126 stars 11 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
70
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Fronius Use this skill for operator-approved Fronius photovoltaic monitoring: local inverter reads through Fronius Solar API V1 and cloud reads through Solar.web Query API. This v1 skill covers read-only monitoring for inverters, meters, storage, OhmPilot, and Solar.web account data. ## Core Contract - Run supported operations through `skills/fronius/fronius.cjs`; the helper is the source of truth for Fronius URLs, Solar.web headers, endpoint bounds, and response-shape metadata. - For the common "what is my solar doing now?" local LAN query, use the helper `local-summary` command. It performs the bounded local Solar API reads and returns normalized live production, consumption, grid, battery, meter, and storage fields. - For live API calls, run the helper to build the request, then pass the emitted `httpRequest` object unchanged to the built-in `http_request` tool. - Use `local-health` through the helper and `http_request` for local reachability checks. - The helper emits only allowlisted endpoint shapes. It rejects arbitrary path passthrough and command-line secret values. - Treat the inverter LAN base URL as plain local configuration. Use `--local-host http://<fronius-ip>` when the operator provides it, or use the configured `FRONIUS_LOCAL_HOST` environment value. - Solar.web Query API authentication uses `AccessKeyId` and `AccessKeyValue` HTTP headers per Fronius' interface documentation. The helper emits those as `secretHeaders` so the gateway...

Details

Author
HybridAIOne
Repository
HybridAIOne/hybridclaw
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

fons

Read and update the user's Fons (fons.vc) presence — founder profile, company profile, product page, investment-readiness checklist, and verified account connections — through the Fons MCP server, and connect that server if it isn't connected yet. Use this whenever the user mentions Fons or fons.vc in any form, wants to edit their founder/company/product profile there, asks about getting their company "investment ready", wants their data room, key metrics, or readiness checklist, wants to verify/connect an account (LinkedIn, GitHub, X, Twitch, Discord, YouTube) on their profile, or asks what they can do on Fons — even if they don't name a specific feature.

3 Updated 6 days ago
Fons-vc
AI & Automation Solid

kronos-agent

Financial time-series forecasting using the Kronos foundation model (MIT, NeoQuasar). Takes OHLC candles, returns predicted future candles with configurable horizon. Infrastructure skill — called by trader agents or scheduled ingestion, not directly invoked by users or the model.

3 Updated yesterday
Silex-Research
AI & Automation Listed

sol-skill

Conventions and tooling for ASU's Sol supercomputer, built around the `solx` CLI. Use whenever a task is happening on Sol - the user mentions Sol or ASU Research Computing, or is clearly on their Sol account (a Sol /scratch path, an sbatch/interactive job, a login/compute node). It covers renewing /scratch files Sol has flagged for deletion (purge/inactivity warnings) via `solx keep` and where to store datasets and model caches; requesting and managing SLURM jobs (the `solx job` interactive-allocation lifecycle, sbatch for batch, GPU and partition/QOS choice, why a job is pending, fairshare-aware and time-aware job management); installing software without sudo (module load, uv for Python, tinytex for LaTeX); reaching a Sol compute-node service like Jupyter from a laptop browser; detecting login-vs-compute nodes and choosing where to run heavy I/O (the DTN, a compute node, or a batch job); and transferring data to and from Sol. Not for generic SLURM/HPC on other clusters (Phoenix, NERSC, ...), cloud GPUs, or p

3 Updated 1 weeks ago
Shu-Wan