← Back to Skills Marketplace
Pingcode Timelogger
by
huuuwnnn-droid
· GitHub ↗
· v1.1.0
· MIT-0
109
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install pingcode-timelogger
Description
Automate PingCode timesheet filling — create sub-tasks and log work hours. Use when asked to fill PingCode timesheets, log work hours, create work items, or...
Usage Guidance
This skill is coherent for PingCode timesheet automation, but it needs sensitive files: a PingCode cookie file and optionally a Git token file. Before installing, ensure you: 1) only place these credential files in the skill's config directory and protect their filesystem permissions; 2) prefer a least-privilege token (Git token scoped to read commits only); 3) confirm your OpenClaw environment provides browser-automation capabilities if you expect the fallback to work; 4) test first on a non-production or sandbox account to confirm behavior; and 5) verify the agent shows the planned changes and you explicitly confirm before any modifications (the SKILL.md requires this).
Capability Analysis
Type: OpenClaw Skill
Name: pingcode-timelogger
Version: 1.1.0
The skill is designed to automate PingCode timesheet entries and integrates with Git providers (GitHub/GitLab) to generate work logs from commit history. While it handles sensitive data such as PingCode cookies and Git tokens stored in `~/.openclaw/skills/pingcode-timelogger/`, its instructions in `SKILL.md` explicitly mandate user confirmation before performing any write operations and focus strictly on the stated functionality. There are no indicators of data exfiltration, unauthorized remote execution, or malicious prompt injection.
Capability Tags
Capability Assessment
Purpose & Capability
Name/description (PingCode timesheet automation, create sub-tasks, log hours, optional Git-sourced tasks) align with the instructions: the SKILL.md only asks for PingCode URL/cookie, project IDs, and optional Git token and repos. There are no unrelated credentials, binaries, or external services requested that would conflict with the stated purpose.
Instruction Scope
Instructions are narrowly scoped to: read the skill config at ~/.openclaw/skills/pingcode-timelogger/config.yaml, use the cookie file for API calls, call PingCode API endpoints, and optionally call GitHub/GitLab APIs to fetch commits. The skill also describes a browser-automation fallback that asks the user to log in via their browser. This is expected functionality, but the fallback relies on the agent/platform having browser-automation capability (Playwright/Selenium/etc.), which the SKILL.md does not declare — an implementation detail to verify.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is downloaded or written by the skill itself. This is low-risk from an install perspective.
Credentials
The skill uses sensitive artifacts (PingCode cookies and optional git token files) stored under the skill config directory. These are proportionate to the task (session cookie or API token are required to call PingCode/Git APIs). Registry metadata lists no required environment variables — the skill relies on config files instead. Users should be aware that these files contain credentials and must be protected; the skill will read them on invocation.
Persistence & Privilege
No 'always: true' flag; skill is user-invocable and allows autonomous invocation (platform default). It does not request system-wide configuration or other skills' credentials. It reads and writes only its own config directory as documented.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install pingcode-timelogger - After installation, invoke the skill by name or use
/pingcode-timelogger - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.0
Add Mode B phased structure for RD-IT project, fix estimated_workload unit (hours not seconds), add pilot_id requirement, add mandatory user confirmation workflow
v1.0.0
pingcode-timelogger 1.0.0
- Initial release: automates PingCode timesheet filling, including creating sub-tasks, setting properties, and logging work hours.
- Supports both manual entry and auto-generating timesheets from Git commits.
- Handles authentication via API (cookie-based) and provides browser automation fallback if API calls fail.
- Configurable via YAML file; first-time users are guided through setup and credential validation.
- Distributes work hours across weekdays, maps work categories, and confirms actions with users before creating records.
- Robust error handling ensures smooth operation and fallback options.
Metadata
Frequently Asked Questions
What is Pingcode Timelogger?
Automate PingCode timesheet filling — create sub-tasks and log work hours. Use when asked to fill PingCode timesheets, log work hours, create work items, or... It is an AI Agent Skill for Claude Code / OpenClaw, with 109 downloads so far.
How do I install Pingcode Timelogger?
Run "/install pingcode-timelogger" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Pingcode Timelogger free?
Yes, Pingcode Timelogger is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Pingcode Timelogger support?
Pingcode Timelogger is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Pingcode Timelogger?
It is built and maintained by huuuwnnn-droid (@huuuwnnn-droid); the current version is v1.1.0.
More Skills