AI Agent Hub
Back to skills
TrustMeImWorking icon

TrustMeImWorking

Life Service Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please install @user_541601ff/trustmeimworking according to https://skillhub.cn/install/skillhub.md.

About this skill

What Problem It Addresses

Some AI usage reviews treat token-call trends as evidence of active work. When quota is allocated daily or weekly but real tasks arrive irregularly, the account can look underutilized or bursty. TrustMeImWorking is a straightforward tool for that gap: it spreads an approved token budget across scheduled windows so the call pattern resembles ongoing work rather than a one-off spike.

How It Works

It runs as a background daemon and calls a configured LLM API at controlled intervals:

  • Work Simulation: fires during weekday work hours with job-related prompts such as code review, architecture design, and data analysis.
  • Spread: distributes the day's budget evenly across the remaining hours for a smoother consumption curve.
  • Immediate: starts consumption right away and resets at 00:00 the next day.

Setup is usually generated by an interactive wizard. It supports OpenAI, DeepSeek, Anthropic, Gemini, Groq, and OpenAI-compatible local or enterprise endpoints. Key fields include Base URL, model, API key stored in local config.json, weekly token budget, job description, and work hours. After startup, a dashboard refreshes every two seconds, and operators can inspect logs, status, run a single session, or use dry-run simulation.

Limits and Caveats

It addresses usage pacing, not business output. If an organization requires actual tasks, code, or documentation, this tool does not replace those deliverables. API keys should be treated as local secrets, and enterprise gateways may need proxy, JWT, or mTLS settings.

Use Cases

  • A team reviews weekly AI usage and needs to spread today's token budget across the remaining hours within cap.
  • An engineer wants to consume an enterprise gateway quota before Friday with code-review prompts in work mode.
  • A developer on an Ollama or vLLM OpenAI-compatible endpoint wants to consume remaining daily quota and inspect logs.
  • A compliance check requires calls during weekday 09:00-18:00, so an admin sets work hours and timezone via wizard.

Best For

  • Engineering leads facing weekly AI-usage reviews: maintain a stable token-call curve in low-demand periods.
  • Ops engineers managing enterprise LLM gateway accounts: schedule quota consumption by budget, hours, and endpoint.
  • Developers using Ollama or vLLM local endpoints: control remaining quota and inspect dry-run status.
  • Test engineers integrating OpenAI, DeepSeek, or Gemini-compatible APIs: trial call pacing on shared accounts.