devrevInteract with DevRev to create/update issues and tickets, and search/query works and parts. Use when asked to create a DevRev issue or ticket, update an exis...
Install via ClawdBot CLI:
clawdbot install nimit2801/devrevGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → https://api.devrev.ai/works.getCalls external URL not in known-safe list
https://api.devrev.ai`AI Analysis
The skill interacts exclusively with the documented, official DevRev API (api.devrev.ai) for its stated purpose of managing issues and tickets. The 'UNKNOWN_DATA_SINK' signal is a false positive, as the POST request to 'works.get' is a standard API call to retrieve a specific work item, not an exfiltration endpoint. No credential harvesting, hidden instructions, or obfuscation are present.
Audited Apr 16, 2026 · audit v1.0
Generated Mar 22, 2026
A development team uses this skill to create and manage issues for bug reports and feature requests. They can list open issues, update statuses as work progresses, and assign issues to specific developers, streamlining their agile workflow.
A support team employs this skill to handle customer tickets by creating new tickets, updating them with resolutions, and searching for open tickets. This helps prioritize high-severity issues and track response times efficiently.
Product managers utilize this skill to create issues for new features, assign them to parts like products or enhancements, and filter works by stage to monitor development progress and align with release cycles.
An IT operations team leverages this skill to log incidents as tickets with severity levels, update them during resolution, and list closed works for post-mortem analysis, ensuring quick handling of critical system issues.
QA testers use this skill to report bugs by creating issues with detailed descriptions, linking them to specific product parts, and tracking them through stages like triage and completion for thorough testing cycles.
Companies offer DevRev as a cloud-based platform with tiered subscriptions for teams of different sizes. Revenue is generated through monthly or annual fees based on user counts and feature access, targeting businesses needing issue and ticket management.
Large organizations purchase enterprise licenses for DevRev, including custom integrations and dedicated support. Revenue comes from one-time license fees or annual contracts, often with additional charges for premium features and scalability.
DevRev provides a free tier for small teams with basic issue tracking, then upsells to paid plans for advanced features like API access, analytics, and priority support. Revenue is driven by converting free users to premium subscriptions.
💬 Integration Tip
Ensure the DEVREV_TOKEN environment variable is set correctly and use DON IDs for all API calls, as display IDs are not supported in requests.
Scored Apr 19, 2026
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking....
Governed loop with roadmap, budget, ledger, and understanding debt.
Create a first-hour action log for home water leaks with shutoff checklist, photo checklist, damage notes, contacts, and cleanup timeline.
Create a short-term home recovery log for a cold, flu, or similar illness, including symptom timeline, temperature entries, hydration and rest notes, user-en...
The meta-framework for how a company runs — the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native,...
Use when synchronizing frontend project documentation with source-of-truth files such as package.json, lockfiles, config, env examples, routes, API clients o...