Verified Research
sweetcornna/free-search-mcp
Use with the free-search MCP tools whenever a web lookup must yield facts someone will rely on: dates, deadlines, prices, prizes, fees, rules, eligibility, schedules, versions, statistics, news, or…
Integrates with TimeDoctor API to pull employee time tracking data, worklogs, statistics, and productivity metrics using simple Python scripts
$ npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills timedoctor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/timedoctor-skill .claude/skills/timedoctor && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "timedoctor" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/timedoctor-skill into .claude/skills/timedoctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "timedoctor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/timedoctor-skillType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills timedoctor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/timedoctor-skill .agents/skills/timedoctor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "timedoctor" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/timedoctor-skill into .agents/skills/timedoctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "timedoctor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills timedoctor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/timedoctor-skill .cursor/skills/timedoctor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "timedoctor" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/timedoctor-skill into .cursor/skills/timedoctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "timedoctor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/timedoctor-skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills timedoctor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/timedoctor-skill .gemini/skills/timedoctor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "timedoctor" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/timedoctor-skill into .gemini/skills/timedoctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "timedoctor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills timedoctorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/timedoctor-skill .github/skills/timedoctor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "timedoctor" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/timedoctor-skill into .github/skills/timedoctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "timedoctor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills timedoctor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/timedoctor-skill .opencode/skills/timedoctor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "timedoctor" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/timedoctor-skill into .opencode/skills/timedoctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "timedoctor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
timedoctorIntegrates with TimeDoctor API to pull employee time tracking data, worklogs, statistics, and productivity metrics using simple Python scripts
Timedoctor is an agent skill from LeoYeAI/openclaw-master-skills. Integrates with TimeDoctor API to pull employee time tracking data, worklogs, statistics, and productivity metrics using simple Python scripts
Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `README.md`, `_meta.json` and `timedoctor.py`).
It sits in Productivity & Automation, covering Time tracking and reporting and Statistics. It works with Python. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
python3pip3From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
TIMEDOCTOR_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Timedoctor loads about 4.6k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 1,264 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,264 words, ~4,637 tokens.
.claude/skills/timedoctor/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Interact with TimeDoctor API for employee time tracking, activity logs, productivity statistics, and workforce analytics using simple Python CLI commands.
Provides direct access to TimeDoctor's time tracking API through a Python CLI tool. Execute commands, get JSON data, present formatted results to users.
Option 1: Easy Setup (Recommended)
Just provide your TimeDoctor email and password:
python3 timedoctor.py login --email "your-email@company.com" --password "your-password"This returns a JWT token valid for 6 months. Copy the token and set it:
export TIMEDOCTOR_TOKEN="your-jwt-token-from-login-response"Option 2: Manual Token Setup
If you already have a token or prefer manual setup:
# Required
export TIMEDOCTOR_TOKEN="your-jwt-token"
# Optional (can be discovered via get_authorization)
export TIMEDOCTOR_COMPANY_ID="your-company-id"For Multiple Accounts: Users can switch accounts by changing the token:
# Account 1
export TIMEDOCTOR_TOKEN="token-for-account-1"
export TIMEDOCTOR_COMPANY_ID="company-id-1"
# Account 2
export TIMEDOCTOR_TOKEN="token-for-account-2"
export TIMEDOCTOR_COMPANY_ID="company-id-2"Quick Setup Workflow:
# 1. Login to get token
python3 timedoctor.py login --email "user@company.com" --password "password"
# 2. Copy token from response and set it
export TIMEDOCTOR_TOKEN="1jxExVs9WGsWccrq2ysMKMZVZlTVyTZc15tlgcWF_Qns"
# 3. Discover available companies
python3 timedoctor.py get_authorization
# 4. Set company ID (optional)
export TIMEDOCTOR_COMPANY_ID="aFtR8crWxHTeLzIm"
# 5. Start using commands
python3 timedoctor.py get_today_worklog --company-id $TIMEDOCTOR_COMPANY_IDAll commands follow this pattern:
python3 timedoctor.py COMMAND [--company-id ID] [OPTIONS]The script is located in the skill directory and returns JSON output.
Login (Get JWT Token):
python3 timedoctor.py login --email "user@company.com" --password "password"Returns: JWT token valid for 6 months
Discover Available Companies:
python3 timedoctor.py get_authorizationReturns: User info and list of accessible companies with IDs
Today's Activity:
python3 timedoctor.py get_today_worklog --company-id COMPANY_IDThis Week's Stats:
python3 timedoctor.py get_this_week_stats --company-id COMPANY_IDThis Month's Stats:
python3 timedoctor.py get_this_month_stats --company-id COMPANY_IDCustom Date Range:
python3 timedoctor.py get_worklog \
--company-id COMPANY_ID \
--from-date "2024-03-01T00:00:00Z" \
--to-date "2024-03-31T00:00:00Z"List Users:
python3 timedoctor.py get_users --company-id COMPANY_IDList Projects:
python3 timedoctor.py get_projects --company-id COMPANY_IDFilter by Users:
python3 timedoctor.py get_today_worklog --company-id COMPANY_ID --user-ids "123,456,789"TimeDoctor User Account (requires TIMEDOCTOR_TOKEN)
└── Company A (ID: 12345)
├── User 1
├── User 2
└── Projects...
└── Company B (ID: 67890)
├── User 3
├── User 4
└── Projects...
└── Company C (ID: 11111)
└── Users...One Token = One User Account
One Account Can Access Multiple Companies
--company-idDifferent User Accounts Need Different Tokens
Scenario 1: User with Multiple Companies
User: "Show my companies"
Agent: Runs get_authorization
Response shows:
- Acme Corp (12345)
- Beta Startup (67890)
- Gamma LLC (11111)
Agent: "You have access to 3 companies. Which one?"
User: "Acme Corp"
Agent: Uses --company-id 12345 for all subsequent requestsScenario 2: Switching Companies
User: "Now show me Beta Startup's data"
Agent: Remembers Beta Startup = 67890 from earlier
Agent: Uses --company-id 67890
No token change needed!Scenario 3: Switching User Accounts
User: "I want to use my other TimeDoctor account"
Agent: "You need to update your token. Run:
export TIMEDOCTOR_TOKEN='your-other-token'"
User: Updates token
Agent: Runs get_authorization with new token
Agent: Shows new list of companies for that accountFollow this workflow:
Check if User Has Token
TIMEDOCTOR_TOKEN is not set, help them login:"To get started, I need your TimeDoctor credentials.
I'll run: python3 timedoctor.py login --email YOUR_EMAIL --password YOUR_PASSWORD
What's your TimeDoctor email and password?"export TIMEDOCTOR_TOKEN="extracted-token"Discover and Present Available Companies
get_authorization first if company_id is not knownYou have access to these TimeDoctor companies:
1. Company A (ID: 12345)
2. Company B (ID: 67890)
3. Company C (ID: 11111)
Which company would you like to use?Execute Appropriate Command
--company-id parameter with the selected companyHandle Multiple Accounts
Parse and Format Output
{"error": "..."} firstError Recovery
"TIMEDOCTOR_TOKEN environment variable not set" → Help user login with email/password"company_id required" → Run get_authorization to discover companies"401 Unauthorized" → Token expired, user needs to login again (6-month validity)ALWAYS use ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ
Examples:
2024-03-22T00:00:00Z2024-03-23T00:00:00Z2024-03-22T00:00:00Z to 2024-03-23T00:00:00ZCalculating Dates:
get_today_worklog (automatic)get_this_week_stats (automatic, Monday to today)get_this_month_stats (automatic, 1st to today)get_worklog or get_stats_totalFor Worklogs:
For Statistics:
For Lists (users, projects, tasks):
User: "I want to use TimeDoctor"
Steps:
1. Check if TIMEDOCTOR_TOKEN is set
2. If not, ask for credentials:
"To get started, I need your TimeDoctor login credentials.
What's your TimeDoctor email and password?"
3. User provides: "email@company.com" and "password123"
4. Run: python3 timedoctor.py login --email "email@company.com" --password "password123"
5. Parse response and extract token
6. Tell user:
"Great! I got your token. It's valid for 6 months (until September 2026).
Please set it in your environment:
export TIMEDOCTOR_TOKEN='1jxExVs9WGsWccrq2ysMKMZVZlTVyTZc15tlgcWF_Qns'
Once set, I can pull your TimeDoctor data."
7. After user confirms, proceed to Workflow 1 to discover companiesUser: "Show me today's activity"
Steps:
1. Check if you know the company_id for this session
2. If not, run: python3 timedoctor.py get_authorization
3. Parse response and present companies:
"I found these TimeDoctor companies you have access to:
1. Acme Corp (ID: 12345) - 45 users
2. Beta Inc (ID: 67890) - 12 users
3. Gamma LLC (ID: 11111) - 8 users
Which company would you like to check?"
4. User responds: "Acme Corp" or "1" or "12345"
5. Remember company_id = 12345 for this session
6. Run: python3 timedoctor.py get_today_worklog --company-id 12345
7. Parse JSON and create table:
| User | Hours Worked | Productive % | Projects |
8. Add summary: "Total: X hours across Y users"User: "Show today's activity for the team"
Steps:
1. Use remembered company_id from session
2. Run: python3 timedoctor.py get_today_worklog --company-id COMPANY_ID
3. Parse JSON and create table:
| User | Hours Worked | Productive % | Projects |
4. Add summary: "Total: X hours across Y users"User: "Show me stats for Beta Inc instead"
Steps:
1. Run: python3 timedoctor.py get_authorization
2. Find "Beta Inc" in the companies list
3. Extract company_id (67890)
4. Update session to remember new company_id
5. Confirm: "Switched to Beta Inc (ID: 67890)"
6. Run requested command with new company_idUser: "Show today's activity for the team"
Steps:
1. Check if TIMEDOCTOR_COMPANY_ID is set in environment
2. If not, run: python3 timedoctor.py get_authorization
3. Extract company_id from response
4. Run: python3 timedoctor.py get_today_worklog --company-id COMPANY_ID
5. Parse JSON and create table:
| User | Hours Worked | Productive % | Projects |
6. Add summary: "Total: X hours across Y users"User: "How much did John work this week?"
Steps:
1. Run: python3 timedoctor.py get_users --company-id COMPANY_ID
2. Find John's user_id in response
3. Run: python3 timedoctor.py get_this_week_stats --company-id COMPANY_ID --user-ids "JOHN_ID"
4. Parse and present:
- Total hours: X
- Productive time: Y (Z%)
- Top projects: ...
- Daily breakdown: Mon: X hrs, Tue: Y hrs, ...User: "How much time was spent on Project Alpha last month?"
Steps:
1. Run: python3 timedoctor.py get_projects --company-id COMPANY_ID
2. Find "Project Alpha" and get its project_id
3. Calculate last month's date range (1st to last day)
4. Run: python3 timedoctor.py get_stats_total \
--company-id COMPANY_ID \
--from-date "YYYY-MM-01T00:00:00Z" \
--to-date "YYYY-MM-31T23:59:59Z" \
--project-id PROJECT_ID
5. Present breakdown by user and totalUser: "I want to use my other TimeDoctor account"
Steps:
1. Explain: "To switch to a different TimeDoctor user account, you need to update your token."
2. Provide instructions:
"Please run these commands with your other account's token:
export TIMEDOCTOR_TOKEN="your-other-account-token"
Then let me know when you're ready."
3. After they confirm, run: python3 timedoctor.py get_authorization
4. Present available companies for the new account:
"Now connected as [User Name]. You have access to:
1. Company X (ID: 99999)
2. Company Y (ID: 88888)
Which company would you like to use?"
5. Remember the selected company_id for this sessionOnce a user selects a company, remember it for the entire conversation session:
Session State:
- current_company_id: 12345
- current_company_name: "Acme Corp"
- current_token_user: "john@acme.com"Ask user to select company again when:
You have access to these TimeDoctor companies:
1. Acme Corporation (ID: 12345)
- 45 active users
- Role: Admin
2. Beta Startup (ID: 67890)
- 12 active users
- Role: Manager
3. Gamma Consulting (ID: 11111)
- 8 active users
- Role: User
Which company would you like to use? (Enter number, name, or ID)Available companies:
• Acme Corporation (12345)
• Beta Startup (67890)
• Gamma Consulting (11111)
Which one?You have access to: Acme Corporation (ID: 12345)
I'll use this company for your requests.Accept any of these formats:
Match flexibly:
login - Login with email/password to get JWT token (valid 6 months)get_authorization - Get user info and available companiesget_companies - List all accessible companiesget_company - Get specific company detailsget_users - List users in companyget_user - Get specific user detailsget_managed_users - Get users managed by a managerget_activity_worklog - Detailed work activity logget_activity_timeuse_stats - Time usage statisticsget_disconnectivity - Offline/disconnected periodsget_today_worklog - Today's worklog (convenience)get_stats_total - Aggregated total statisticsget_stats_category - Stats by productivity category (4=Productive, 3=Neutral, 2=Unproductive, 0=Unrated)get_stats_summary - Summary stats over timeget_stats_work_life - Work-life balance statsget_stats_shift - Shift compliance statsget_stats_outliers - Unusual activity patternsget_this_week_stats - This week's stats (convenience)get_this_month_stats - This month's stats (convenience)get_timesheet_total - Timesheet totalsget_timesheet_summary - Timesheet summaryget_projects - List projectsget_project - Get project detailsget_tasks - List tasksget_task - Get task detailsget_groups - List groups/teamsget_group - Get group detailsget_work_schedules - List work schedulesget_work_schedule - Get schedule detailsget_work_schedule_issues - Schedule violationsget_leave_stats - Leave/time-off statsget_users_payroll - User payroll infoget_company_payroll_settings - Company payroll settingsget_files - Screenshots/screencastsget_categories - Productivity categoriesget_unrated_categories_count - Count of unrated itemsCommon options across commands:
--company-id COMPANY_ID - Required for most commands--user-ids "123,456" - Filter by specific users (comma-separated)--from-date "2024-03-01T00:00:00Z" - Start date (ISO 8601)--to-date "2024-03-31T00:00:00Z" - End date (ISO 8601)--project-id PROJECT_ID - Filter by project--page 1 - Page number for pagination--limit 100 - Results per page (max 1000){"error": "..."} in JSON outputget_today_worklog is easier than calculating today's dates--page and --limit| Error | Cause | Solution |
|---|---|---|
TIMEDOCTOR_TOKEN environment variable not set | Token not configured | User needs to set export TIMEDOCTOR_TOKEN="..." |
company_id required | Missing company ID | Run get_authorization to discover company_id |
401 Unauthorized | Token expired or invalid | User needs new token (6-month validity) |
httpx module not found | Dependencies not installed | Run pip3 install -r requirements.txt |
| No data returned | No activity in date range | Check date range and verify users have activity |
JehadurRE (Jehadur Rahman Emran)
MIT
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files in skills/timedoctor-skill of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Timedoctor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Timedoctor this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Verified Researchsweetcornna/free-search-mcp | 126 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Process InboxTDesktop-x64/tdesktop | 3k | 1 repos | ~4.3k | Automated safety check: Pass | GPL-3.0 | |
| Process Inboxtelegramdesktop/tdesktop | 33k | — | ~5.4k | Automated safety check: Pass | GPL-3.0 | |
| Telegrambubbuild/bub | 1.7k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Browser Use Terminalbrowser-use/terminal | 652 | — | ~2.1k | Automated safety check: Pass | MIT |
sweetcornna/free-search-mcp
Use with the free-search MCP tools whenever a web lookup must yield facts someone will rely on: dates, deadlines, prices, prizes, fees, rules, eligibility, schedules, versions, statistics, news, or…
TDesktop-x64/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
bubbuild/bub
Telegram Bot skill for sending and editing Telegram messages via Bot API.
browser-use/terminal
Direct browser control via the Browser Use Terminal CLI. An agent skill from browser-use/terminal.
robocorp/robocorp
Bootstrap from an empty folder or build, debug, locally run, and validate Python automations built with Robocorp or Sema4.ai tooling, robocorp.tasks, rcc, robocorp-browser, and RPA Framework.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Works with
Categories
Integrates with TimeDoctor API to pull employee time tracking data, worklogs, statistics, and productivity metrics using simple Python scripts. Timedoctor is an agent skill from LeoYeAI/openclaw-master-skills.
Timedoctor fits situations like: tasks that involve Time tracking and reporting; tasks that involve Statistics.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a claude-code`. Or copy the skill folder (skills/timedoctor-skill in LeoYeAI/openclaw-master-skills) into .claude/skills/timedoctor in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a codex`. Or copy the skill folder (skills/timedoctor-skill in LeoYeAI/openclaw-master-skills) into .agents/skills/timedoctor in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill timedoctor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/timedoctor, .gemini/skills/timedoctor, .github/skills/timedoctor and .opencode/skills/timedoctor in your project.
Going by SKILL.md and its folder, Timedoctor needs Python for the scripts in its folder, the command-line tools its instructions call (python3 and pip3) and credentials named TIMEDOCTOR_TOKEN. Our summary lists: Python 3; A credential in TIMEDOCTOR_TOKEN.
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Timedoctor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.6k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Timedoctor: Verified Research (sweetcornna/free-search-mcp, 126 stars), Process Inbox (TDesktop-x64/tdesktop, 3k stars), Process Inbox (telegramdesktop/tdesktop, 33k stars) and Telegram (bubbuild/bub, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.