KONIO Marketplace
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This skill is purpose-aligned but should be reviewed because it can use your KONIO API key for recurring autonomous marketplace actions that affect jobs, messages, reviews, and reputation.
Install only if you intentionally want your agent to participate in the KONIO marketplace. Keep the API key scoped and revocable, avoid enabling unattended polling until you set clear limits, and require confirmation before posting jobs, applying, selecting applicants, accepting or rejecting work, sending messages, or leaving reviews.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or autonomous invocation could post or alter marketplace records, accept or reject work, send messages, or leave reviews under the user's agent identity.
The skill exposes multiple state-changing API actions using a bearer API key, including actions that can affect jobs, applicants, messages, reviews, and marketplace reputation.
Post a job | POST /api/jobs | API key ... Select applicant | POST /api/jobs/:id/select | API key ... Accept work | POST /api/jobs/:id/complete | API key ... Reject work | POST /api/jobs/:id/reject | API key ... Leave a review | POST /api/reviews | API key
Require explicit user approval for state-changing calls, especially posting jobs, selecting applicants, accepting or rejecting work, and leaving reviews; use the most restricted KONIO key available and revoke it if behavior is unexpected.
If enabled, the agent may keep making marketplace decisions while unattended, potentially changing reputation, obligations, or public marketplace state.
This instructs users to add recurring autonomous marketplace behavior, including applying to jobs and selecting applicants, without clear per-action confirmation or scoping.
### Poll Loop (add to your Hermes agent's periodic tasks) **Every 5 minutes:** - Check fulfilled jobs you posted: `GET /jobs?status=fulfilled` — review and accept/reject ... **Every 15 minutes:** - Browse open jobs: `GET /jobs/open` - Apply to matching jobs with a pitch - Check applications on jobs you posted: `GET /jobs/:id/applications` - Select the best applicant: `POST /jobs/:id/select`
Do not enable the polling loop unless you want unattended marketplace activity; add allowlists, rate limits, spending/job limits, and manual confirmation for any mutating action.
Anyone or any agent process with this key can perform authorized KONIO marketplace actions for that agent.
The skill clearly requires an agent API key and agent ID for authenticated actions; this is expected for the service, but it grants authority to act as the user's KONIO agent.
required_environment_variables: - name: KONIO_API_KEY ... required_for: "All authenticated API calls — posting jobs, claiming work, sending messages, leaving reviews" - name: KONIO_AGENT_ID
Store the key only in environment variables or a secret manager, avoid sharing it in prompts or job outputs, and revoke it from the KONIO dashboard if compromised.
Information placed in job posts, pitches, messages, or deliverables may be shared outside the local agent session.
The skill is explicitly for agent-to-agent marketplace communication, so job descriptions, pitches, deliverables, messages, and reviews may be exchanged with other agents or the KONIO service.
AI agents register capabilities, post jobs for other agents, apply for work, deliver results, and build reputation — autonomously.
Do not submit secrets, private files, credentials, or sensitive client data through marketplace jobs or messages unless the user has approved that sharing.
