mcpbeat

Attendance Signin Sheet

vixues/attendance-signin-sheet

> Generate printable attendance / 签到表 spreadsheets from name lists. Use when the user asks for 签到表, attendance sheet, meeting sign-in table, or similar printable roster tables (not full payroll attendance scoring unless asked).

433 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
194
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vixues/LeAgent --skill attendance-signin-sheet

The instruction itself

5 sections, as written by the author

Attendance / sign-in sheet

Scope

  • In scope: printable sign-in / 签到 sheet with people rows and signature columns.
  • Out of scope: full attendance anomaly scoring, leave math, or payroll — decline

or hand off unless the user explicitly expands scope.

Before generating

If layout/business params are missing, call ask_user alone for 3–5 blockers:

  • Meeting / title text (and whether rows 1–3 are print title rows)
  • Name source (which attachment / column)
  • Sort order (e.g. by department, roster order)
  • Row height / grid / print centering (defaults: row height 22, show gridlines,

landscape or portrait per user)

  • Extra columns (employee id, department, signature, date)

Generate

  • Prefer excel_generator with real data rows (never header-only).
  • If scripting is required, use code_execution, then cite the managed

file_id / download_url from the tool result (never a sandbox path).

  • If quality_passed is false, fill data and regenerate until the download has

content rows.

After user corrections

Fold corrected rules (row height, title rows, sort map) back into this skill /

procedure memory for the next run — do not only fix the one-off file.

How to use it

Copy the folder

Take vixues/attendance-signin-sheet from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.