Agriculture
v1.0.0Farm operations management — crop planning, inventory, equipment, livestock, weather, and financials.
⭐ 0· 68·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the SKILL.md content: planning, inventory, equipment, livestock, weather, and financial monitoring. There are no required binaries, config paths, or credentials that don't belong to farm operations.
Instruction Scope
SKILL.md defines detailed, scoped operational procedures (heartbeats, planting schedules, inventory, alerts). It references external data sources (weather forecasts, commodity/market prices) but does not specify endpoints or ask for unrelated system files or secrets. This is appropriate for the stated purpose, though it leaves how external data is obtained unspecified.
Install Mechanism
Instruction-only skill with no install spec and no code files — minimal disk/write risk and no external installers to audit.
Credentials
The skill declares no required environment variables or credentials, which matches its instruction-only nature. However, practical operation (weather APIs, commodity prices, supplier integrations, or financial systems) will likely require connectors/credentials that the SKILL.md does not enumerate; the absence of requested credentials is not a direct concern but leaves integration details to be handled elsewhere.
Persistence & Privilege
No elevated privileges requested (always is false). The skill does not request to modify other skills or system-wide settings and is user-invocable; autonomous invocation remains possible per platform default.
Assessment
This skill appears coherent and low-risk as distributed: it's a long instruction set describing farm management workflows and doesn't request credentials or install code. Before installing, consider how it will obtain external data (weather feeds, market prices, supplier/catalog APIs, or accounting/financial integrations). Decide which API keys or connectors you will provide and grant only minimal privileges for those services. Also consider where the agent will store farm data and financial records (local vs cloud) and whether you need to restrict the skill's autonomous invocation in settings if you do not want it to act without explicit prompts.Like a lobster shell, security has layers — review code before you run it.
latestvk979ac66r3jh653r2em777fgk984d8na
License
MIT-0
Free to use, modify, and redistribute. No attribution required.