sherpamindUse for SherpaDesk-related requests: ticket lookup, support-history retrieval, account/user/technician analysis, stale-ticket review, workload questions, ope...
Install via ClawdBot CLI:
clawdbot install kklouzal/sherpamindGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/kklouzal/SherpaMindAudited Apr 17, 2026 · audit v1.0
Generated Oct 6, 2026
An IT managed service provider uses SherpaMind to pull stale open tickets, technician workloads, and per-account ticket counts from their SherpaDesk data. Support leads run report-status-counts and open-ticket-ages each morning to prioritize escalations. This keeps the queue moving without manual spreadsheet exports.
A support operations analyst searches historical SherpaDesk tickets and chunks to find prior resolutions for recurring outages or VPN issues. Using search-ticket-chunks and search-vector-index with account and category filters, they surface repeat offenders. Findings feed a knowledge base and root-cause program.
An account manager preparing for a customer business review queries account-summary and recent-account-activity to understand ticket volume, resolution status, and open issues. SherpaMind turns raw SherpaDesk records into a one-page briefing. This supports retention conversations with evidence rather than anecdotes.
A service delivery manager analyzes technician-summary and recent-technician-load to balance staffing across shifts. SherpaMind reveals who is overloaded, what categories dominate, and where resolution times lag. The data informs scheduling and coaching decisions.
A CIO or operations leader asks open-ended questions like 'what were our biggest support themes last quarter' and gets answers grounded in retrieved SherpaDesk evidence. SherpaMind blends structured reports with fuzzy retrieval to produce narrative insights. This reduces dependence on ad hoc analyst requests.
SherpaMind is deployed inside an organization's own IT team as a private query layer over its SherpaDesk instance. It requires live SherpaDesk API credentials and creates workspace-local runtime state for sync and analysis. Value comes from faster triage and better operational visibility.
MSPs embed SherpaMind into their service delivery workflow to monitor multiple client accounts and technician performance. They can run scheduled reports and use retrieval to accelerate ticket resolution. It complements their existing ticketing and RMM stack.
Consultancies or support auditors use SherpaMind during engagements to analyze a client's SherpaDesk data and produce backlog, workload, and recurring-incident reports. The skill's optional background service supports continuous data preparation. Deliverables are billable assessments and remediation roadmaps.
💬 Integration Tip
Requires SherpaDesk API credentials staged under .SherpaMind/private/secrets and org settings in settings.env before live sync works. Use the stable runner python3 scripts/run.py and prefer structured report commands before fuzzy retrieval to keep answers grounded and efficient.
Scored Oct 6, 2026
Generate ideas fast. Adapt depth and structure to what the user actually needs.
Evaluate any AI skill's quality through step-by-step diagnosis — measuring trigger accuracy, per-step execution (completion/correctness/quality), efficiency,...
通过调用 Prana 平台上的远程 agent 完成以下处理:基于100个热门TradingView Pine Script指标转换的Python技术分析工具集,提供专业的技术指标计算、分析和可视化功能 IMPORTANT: This skill has a mandatory step-by-step proc...
Provides a structured screening for stress perception using the PSS-10 scale as an independent skill in ClawHub.
Spawns real AI-powered OpenClaw sub-sessions to run multiple specialized agents concurrently for content, dev, QA, docs, and autonomous workflows.
Provides comprehensive analysis and comparison of global AI regulations, safety incidents, model evaluations, standards, and international governance for pol...