timesheet
Skill1 starsChanged 7 months agoMITView on GitHub
Use when the user wants to submit today's ERPNext timesheet, log work hours, fill in a timesheet from conversation history, or make a backdated timesheet entry for a previous date. Uses MCP tools to interact with ERPNext.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- JHostalek/dotclaudetheir own version, first seen Nov 1, 2026
- wearedevpunks/skillstheir own version, first seen Oct 13, 2026
- ZunoSmartLabs/zsl-superpowerstheir own version, first seen Sep 21, 2026
- lounisch/claude-skill-timesheettheir own version, first seen May 18, 2026
- cgbarlow/skillstheir own version, first seen May 4, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- cgbarlow/skills★ 18same name
- JHostalek/dotclaude★ 11same name
- ZunoSmartLabs/zsl-superpowers★ 2same name
- lounisch/claude-skill-timesheet★ 1same name
- wearedevpunks/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 6 are distinctive, and 14 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Resolve the target date: Read the invocation message:
- Very specific: line 18
If it specifies a past date (e.g.
- Distinctive: line 49
Default Activity: always offer these 4 options: Development, Development Testing, Debugging, Debug & Fix — plus the user can type Other for …
- Very specific: line 51
Call updateSettings with the selected project and activity_type.
- Very specific: line 63
Call TaskUpdate on TASK_READ, status: in_progress.
- Very specific: line 85
If ENTRIES is already set from Step 1 (agent output), skip to listTasks.
- Very specific: line 97
Call listTasks with project=STATUS.project silently.
- Very specific: line 111
After classifying all entries, group the ⚠ entries by shared topic keywords (e.g.
- Distinctive: line 117
Do these three sub-steps in strict order — do not call any tool until the draft text has been output to the user:
- Distinctive: line 121
If overdue tasks were identified in Step 2, list them first:
- Very specific: line 146
3b. Only after the draft text is output: Call TaskUpdate on TASK_SYNTH, status: completed.
- Very specific: line 148
3c. Then: Call TaskUpdate on TASK_DRAFT, status: in_progress.
- Very specific: line 182
If an existing Task Group selected: set entry.parent_task = group.name.
- Very specific: line 183
If No Task Group: leave both unset.
- Very specific: line 193
If an existing task selected: set entry.task = task.name.
- Very specific: line 215
If Make changes: wait for a freeform edit instruction.
- Very specific: line 218
Empty entries: if no entries, ask the user to add some first.
- Very specific: line 219
Hours mismatch: if total ≠ STATUS.work_hours, note it: "Total is Xh, default is Yh — submit anyway?"
- Distinctive: line 232
Delete entry → remove, recalculate hours, re-render draft
- Distinctive: line 233
Add entry → append, re-render draft
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ERPNext Timesheet
Automate daily ERPNext timesheet filling from your Claude conversation history.
When this skill is invoked, follow these steps exactly. Do not skip steps. Before the draft (Steps 0–2): no narration — no "Starting Step N", no "checking X", no intermediate announcements. The only output before the draft is the setup prompt or announce line. During Step 3: use AskUserQuestion as specified.
Step 0: Setup and Date Resolution
Resolve the target date. Read the invocation message:
- If it specifies a past date (e.g. "for yesterday", "for 2026-03-24", "last Friday") — resolve it to
YYYY-MM-DDand store asTARGET_DATE. - Otherwise use today's date.
Call checkConfig silently. Store the result as CONFIG.
If CONFIG.configured is false and reason is credentials_missing:
Your ERPNext credentials aren't configured. Run
/plugin→ Installed → erpnext-timesheet → Configure Options to enter your URL, username, and password, then re-run/timesheet.
Stop here.
If CONFIG.configured is false and reason is auth_failed:
ERPNext authentication failed. Run
/plugin→ Installed → erpnext-timesheet → Configure Options to update your credentials, then re-run/timesheet.
Stop here.
If CONFIG.configured is false and reason is connection_error:
Could not connect to your ERPNext instance. Check that your URL is correct and the server is reachable, then re-run
/timesheet.
Stop here.
If the invocation message mentions reconfiguring, changing credentials, or updating settings: tell the user to run /plugin → Installed → erpnext-timesheet → Configure Options, then re-run /timesheet. Stop here.
If CONFIG.configured is true:
If project or default_activity is empty:
Credentials are saved but defaults are missing. Use AskUserQuestion with two questions using CONFIG._projects and CONFIG._activity_types:
- Default Project: up to 4 options from
_projects(showlabel, value isid); mark current default as "(Selected)" - Default Activity: always offer these 4 options: Development, Development Testing, Debugging, Debug & Fix — plus the user can type Other for anything else
Call updateSettings with the selected project and activity_type. Store the return value as STATUS — it has the full configured shape. Proceed to Step 1.
Otherwise build STATUS directly from CONFIG — configured: true, username, url, project, default_activity taken directly; work_hours defaults to 8 if absent.
Announce: Logging work for TARGET_DATE — <username> on <url>
Create tasks via TaskCreate for the remaining steps. Store their IDs:
TASK_READ: subject "Read conversation history", activeForm "Reading history"TASK_SYNTH: subject "Synthesize entries", activeForm "Synthesizing entries"TASK_DRAFT: subject "Review draft", activeForm "Reviewing draft"TASK_SUBMIT: subject "Submit timesheet", activeForm "Submitting timesheet"
Call TaskUpdate on TASK_READ, status: in_progress.
Proceed to Step 1.
Step 1: Read Work Context
If the user specified a different source (git commits, manual description, a file), use that instead — run git log, read files, or ask. Store the gathered context as RAW_CONTEXT and leave ENTRIES unset.
Otherwise, dispatch the history-reader agent:
TARGET_DATE: {TARGET_DATE}
STATUS: {STATUS as JSON — include project, work_hours, default_activity}Store the agent's JSON output directly as ENTRIES. Dispatch the history-reader agent exactly once — never re-dispatch regardless of the result. If ENTRIES is [] or empty, tell the user briefly and continue to Step 3 with no entries.
Call TaskUpdate on TASK_READ, status: completed.
Call TaskUpdate on TASK_SYNTH, status: in_progress.
Step 2: Fetch Tasks + Match Entries
If ENTRIES is already set from Step 1 (agent output), skip to listTasks. Otherwise, synthesize from RAW_CONTEXT:
- description: concise professional summary, max 80 chars, no filler phrases ("worked on", "helped with")
- hours:
STATUS.work_hours / number_of_tasks, rounded to 1 decimal; last entry absorbs rounding remainder so total equalswork_hoursexactly - activity_type:
STATUS.default_activity - project:
STATUS.project(default; may be overridden per entry during Step 3)
Grouping rules:
- Merge closely related messages (e.g. "fix bug" + "write test for fix" = one entry)
- Ignore meta-conversation (greetings, off-topic chat)
- Focus on deliverables: what was built, fixed, reviewed, or designed
- 1–8 entries
Call listTasks with project=STATUS.project silently. Store as TASKS.
Identify overdue tasks: walk TASKS recursively; collect nodes where exp_end_date is non-empty and exp_end_date < TARGET_DATE. (Completed and Cancelled tasks are excluded at fetch time.)
Auto-match and classify each entry:
For each entry, search TASKS recursively by keyword overlap between the entry description and task subjects:
- ✓ resolved (existing task) — exactly one task has clear keyword overlap. Set
entry.task = task.name. If the matched task has a parent, setentry.parent_task = task.parent_task. Setentry.resolved = true. Setentry.cluster_id = null. - ✓ resolved (new task, group known) — zero tasks match AND exactly one group has clear keyword overlap with the description. Set
entry.parent_task = group.name, leaveentry.taskunset. Setentry.resolved = true. Setentry.cluster_id = null. - ⚠ unresolved — zero matches with no clear group fit, OR two or more tasks share similar keyword overlap (ambiguous). Set
entry.resolved = false.
Cluster unresolved entries:
After classifying all entries, group the ⚠ entries by shared topic keywords (e.g. entries mentioning "MCP", "plugin", "auth" form a cluster). Store each cluster as a list of entry indices. Assign each ⚠ entry a cluster_id (a short label like "mcp-work"); singletons get cluster_id = null.
Store synthesized entries as ENTRIES.
Step 3: Draft Review
Do these three sub-steps in strict order — do not call any tool until the draft text has been output to the user:
3a. Output the draft text.
If overdue tasks were identified in Step 2, list them first:
Overdue tasks: TASK-XXXX — subject (N days overdue), ...
Draft format — each entry is two lines, status marker at column 0:
✓resolved,⚠needs matching- Project is always shown.
- Task Group field: existing name,
[new "Name"]for proposed,/ ? needs matchingif unknown. - Task field:
TASK-XXXX,TASK-XXXX ⚠ Nd(overdue),new task, or? needs matching. - Footer:
N entries need matching — resolving below.only if N > 0; omit if all resolved.
TARGET_DATE — Xh total
──────────────────────────────────────────────────────────────
✓ 1. [Xh] Description one
Activity · PROJ-XXXX / Group Name / TASK-XXXX
✓ 2. [Xh] Description two
Deployment · PROJ-XXXX / Infrastructure / new task
⚠ 3. [Xh] Description three
Development · PROJ-XXXX / ? needs matching
──────────────────────────────────────────────────────────────
N entries need matching — resolving below.3b. Only after the draft text is output: Call TaskUpdate on TASK_SYNTH, status: completed.
3c. Then: Call TaskUpdate on TASK_DRAFT, status: in_progress.
Interactive resolution (only if ⚠ entries exist):
Process clusters before singletons.
Cluster resolution — for each cluster of 2+ ⚠ entries (same cluster_id):
Use AskUserQuestion:
- Question:
Entries {n1}, {n2}, ... seem related to {inferred topic} ({entry.project}) — could not auto-match. What should we do? - Options:
Create Task Group "{suggested name}"— setentry.proposed_groupto the suggested name for all entries in the cluster; then ask for planned completion date usingAskUserQuestion(Task Group "{name}" — planned completion date?with options: TARGET_DATE, end-of-week, end-of-month,Other (I'll type it)); setentry.proposed_group_dateon all cluster entries; mark all resolvedUse existing Task Group— follow up with a secondAskUserQuestionlisting existing Task Groups fromTASKSforentry.project(default project); setentry.parent_taskfor all cluster entries; setentry.resolved = truefor all cluster entriesNo Task Group (root-level tasks)— clearparent_taskandproposed_groupon all cluster entries; mark all resolvedSplit — handle each separately— treat each cluster entry as a singleton below
Per-entry resolution — for singletons and entries split from clusters, in order:
Q1 — Project (skip if entry.project is already set):
Use AskUserQuestion:
- Question:
Entry N — "{description}" — which project? - Options: each item from
CONFIG._projects(showlabel, value isid) +Other (I'll type it)Setentry.projectto the selected id.
Q2 — Task Group (skip if entry.parent_task or entry.proposed_group is already set):
Use AskUserQuestion:
- Question:
Entry N — "{description}" — which Task Group? ({entry.project}) - Options: existing Task Groups from
TASKS(nodes whereis_group=1) +Create new Task Group+No Task Group (root-level task)
If Create new Task Group selected:
- Derive a suggested Task Group name from the entry description (short, title-case, topic-focused — e.g. "MCP Plugin Work", "Auth Refactor"). Use
AskUserQuestionwith the questionName for this Task Group?and options: the suggested name first, thenRename (I'll type it). IfRenameselected, ask for the name as a plain conversational message and wait for their reply; then echoUsing "{name}".before continuing. Setentry.proposed_groupto the chosen name. - Ask for the Task Group planned completion date. Use
AskUserQuestionwith the questionTask Group "{name}" — planned completion date?and options:{TARGET_DATE}(the target date), end-of-week date (auto-compute from TARGET_DATE), end-of-month date (auto-compute from TARGET_DATE),Other (I'll type it). IfOther, ask as a plain conversational message and wait for the reply. Setentry.proposed_group_dateto the chosen date. - Immediately offer to pull in other ⚠ entries that don't yet have a Task Group: use
AskUserQuestionlisting each remaining entry whereresolved = falseandparent_taskandproposed_groupare both unset — as a multi-select. For each entry selected, setentry.proposed_groupto the same name,entry.proposed_group_dateto the same date, and markentry.resolved = true, skipping their Q2/Q3.
If an existing Task Group selected: set entry.parent_task = group.name.
If No Task Group: leave both unset; mark entry.resolved = true.
Q3 — Task (skip if entry.task is set, entry.parent_task is set, entry.proposed_group is set, or entry.resolved is true):
Use AskUserQuestion:
- Question:
Entry N — "{description}" — assign to an existing task? - Options — overdue tasks first, then open tasks, then new:
- Overdue:
TASK-XXXX — {subject} (⚠ Nd overdue) - Open:
TASK-XXXX — {subject} - Last option:
New task (create one under {Task Group name or "root"})
- Overdue:
If an existing task selected: set entry.task = task.name. Mark entry.resolved = true.
If New task: leave entry.task unset. Ask for planned completion date using AskUserQuestion with the question Entry N — planned completion date? and options: {TARGET_DATE} (the target date), end-of-week date (auto-compute from TARGET_DATE), end-of-month date (auto-compute from TARGET_DATE), Other (I'll type it). If Other, ask as a plain conversational message. Set entry.planned_completion_date to the chosen date. Mark entry.resolved = true.
After all entries resolved (or immediately if all resolved from the start):
Re-render the full draft with ✓ on all entries (skip re-render if nothing changed from the initial display):
TARGET_DATE — Xh total
──────────────────────────────────────────────────────────────
✓ 1. [Xh] Description one
Activity · PROJ-XXXX / Group Name / TASK-XXXX
✓ 2. [Xh] Description two
Activity · PROJ-XXXX / [new "Group Name"] / new task
──────────────────────────────────────────────────────────────Use AskUserQuestion:
- Question:
How does this look? - Options:
Looks fine·Make changes
If Make changes: wait for a freeform edit instruction. Apply it (see conversational edits below), re-render the draft, then show this AskUserQuestion again.
If Looks fine:
- Empty entries: if no entries, ask the user to add some first; return to
Make changesflow. - Hours mismatch: if total ≠
STATUS.work_hours, note it: "Total is Xh, default is Yh — submit anyway?" - Call TaskUpdate on
TASK_DRAFT, status:completed. - Use
AskUserQuestion:- Question:
Submit timesheet for {TARGET_DATE}? - Options:
Submit·Cancel
- Question:
- If
Cancel: stop. - If
Submit:- Call TaskUpdate on
TASK_SUBMIT, status:in_progress. - Proceed to Step 4.
- Call TaskUpdate on
Conversational edits (applied when user selects "Make changes"):
- Edit description → update entry, re-render draft
- Delete entry → remove, recalculate hours, re-render draft
- Add entry → append, re-render draft
- Change activity → update
entry.activity_type, re-render draft - Reassign to leaf task → look up leaf tasks (non-group) in
TASKSrecursively, assign, re-render draft - Move to Task Group → look up Task Groups (
is_group=1) inTASKS, setentry.parent_task, clearentry.proposed_group, re-render draft - Change project → set
entry.project, re-fetch tasks if needed, re-run Q2/Q3 for that entry - Redistribute hours → recalculate evenly, re-render draft
- Move to root → clear both
entry.parent_taskandentry.proposed_group, re-render draft
Step 4: Submit
Dispatch the timesheet-submitter agent:
TARGET_DATE: {TARGET_DATE}
STATUS: {JSON — include username, project, work_hours}
ENTRIES: {JSON array — each entry with: description, hours, activity_type, project; include task, parent_task, proposed_group only when set}The agent emits one STEP: line per completed action. Parse the agent's full output and handle each line:
| Agent output | Action |
STEP: check → passed | — |
STEP: check → duplicate_found | Call TaskUpdate on TASK_SUBMIT, status: completed. Output ⚠ A timesheet already exists for {TARGET_DATE}. and return to Step 3 |
STEP: group → "Name" → ID | — |
STEP: task → "desc" → ID | — |
STEP: submit → TS-XXXX | Call TaskUpdate on TASK_SUBMIT, status: completed. Output Done. TS-XXXX |
STEP: error → auth_failed | Call TaskUpdate on TASK_SUBMIT, status: completed. Output: Your ERPNext session has expired. Run /plugin → Installed → erpnext-timesheet → Configure Options to update your credentials, then re-run /timesheet. |
STEP: error → {message} | Show the error, ask "Retry?" — if yes, re-dispatch the agent (max 3 retries total); if no, call TaskUpdate on TASK_SUBMIT, status: completed, then stop |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

