remote-work-tracker – skill Khác cho agent AI

Remote Work Tracker

What it is: Location management.

Overview

Works out the smallest useful Remote Work Tracker setup for the business in front of it, then

builds it only when asked. The default output is a short recommendation, not a

spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on

request, from one field list so they cannot drift apart.

Layer: Layer 8: Operate. Fits: Scale stage. Table code: n/a.

When to Use This Skill

• remote work tracker
• hybrid work log
• work from home register
• location tracker

Also use it when the user says "location management", or describes the same process happening in a

spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces

empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
• "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
• "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
• "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

> Q: How many people work remotely?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a

time, and stop as soon as the remaining answers would not change the output.

• People - How many remote? / Fully or hybrid? / Any location changes?
• Availability - Core hours? / Overlap required? / How communicated?
• Equipment - Equipment provided? / Who approves? / Any cost to the company?
• Current process - Is it tracked now? / Sheet or nothing? / What gets missed?
• Outcome - What do you need? / A roster, a policy record or both?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless

they ask, and it never carries a value the user did not give.

module: remote-work-tracker
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "People": null
  "Availability": null
  "Equipment": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking

Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Track the roster and the agreement, not daily presence. If you need working hours, record the agreed window per person.

Why this one: Remote tracking degrades into monitoring and stops being trusted. Record agreements and the roster, and leave presence out of it.

Workflow: Person recorded → Location and agreement → Equipment issued → Review

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the

requested artifacts. For machine-readable text, keep prose outside the data; for files,

provide a usable link. Report material validation failures or limitations separately.

**A selected Notion output is rendered by notion-manual-import, so route the

Notion step there.** When the user selects Notion, hand that step to

@notion-manual-import: it holds the CSV, the property

mapping, the import steps and the verification checklist, and it renders the Field

Reference below instead of defining a table of its own. Do not restate the mapping

here and do not improvise the import steps. Manual CSV and mapping outputs need no

connection. For requested workspace changes, follow the shared contract: verify actual

tool access and the target before writing. A user saying "connected" is not tool evidence.

Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the

text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user

requests a workbook.

A CSV carries no types, so after it, name the columns

that need a number, date or currency format applied.

Remote Work Entry,Employee Name,Department,Work Location,Week Start,HQ Days,Remote Days,Core Hours Met,Manager,Approved,Notes,Remote ID
"Home, Tue 3 Mar",Aarav Sharma,Delivery,Bengaluru,2026-01-05,3,2,TRUE,Sneha Iyer,TRUE,"February shows two split-location weeks; the travel policy needs a decision either way.",

CREATE TABLE remote_work_tracker (
  remote_work_entry VARCHAR(255),
  employee_name VARCHAR(255),
  department VARCHAR(255),
  work_location VARCHAR(255),
  week_start DATE NOT NULL,
  hq_days NUMERIC NOT NULL,
  remote_days NUMERIC NOT NULL,
  core_hours_met BOOLEAN NOT NULL,
  manager VARCHAR(255),
  approved BOOLEAN NOT NULL,
  notes TEXT,
  remote_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Remote Work Tracker",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Remote Work Entry": { "type": "string" },
      "Employee Name": { "type": "string" },
      "Department": { "type": "string" },
      "Work Location": { "type": "string" },
      "Week Start": { "type": "string", "format": "date" },
      "HQ Days": { "type": "number" },
      "Remote Days": { "type": "number" },
      "Core Hours Met": { "type": "boolean" },
      "Manager": { "type": "string" },
      "Approved": { "type": "boolean" },
      "Notes": { "type": "string" },
      "Remote ID": { "type": "integer" }
  },
  "required": [
      "Week Start",
      "HQ Days",
      "Remote Days",
      "Core Hours Met",
      "Approved"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Remote Work Entry | Title | Use as the database title |
| Employee Name | Text | Leave as Text |
| Department | Text | Leave as Text |
| Work Location | Text | Leave as Text |
| Week Start | Date | Convert to Date |
| HQ Days | Number | Convert to Number |
| Remote Days | Number | Convert to Number |
| Core Hours Met | Checkbox | Convert to Checkbox |
| Manager | Text | Leave as Text |
| Approved | Checkbox | Convert to Checkbox |
| Notes | Text | Leave as Text |
| Remote ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date,

and anything pointing at another table stays relation.

Field Reference

| # | Field | Type | SQL | JSON Schema | Notion | CSV example |

|---:|---|---|---|---|---|---|

| 1 | Remote Work Entry | text | VARCHAR(255) | string | Text | Home, Tue 3 Mar |

| 2 | Employee Name | text | VARCHAR(255) | string | Text | Aarav Sharma |

| 3 | Department | text | VARCHAR(255) | string | Text | Delivery |

| 4 | Work Location | text | VARCHAR(255) | string | Text | Bengaluru |

| 5 | Week Start | date | DATE | string, format: date | Date | 2026-01-05 |

| 6 | HQ Days | number | NUMERIC | number | Number | 3 |

| 7 | Remote Days | number | NUMERIC | number | Number | 2 |

| 8 | Core Hours Met | checkbox | BOOLEAN | boolean | Checkbox | TRUE |

| 9 | Manager | text | VARCHAR(255) | string | Text | Sneha Iyer |

| 10 | Approved | checkbox | BOOLEAN | boolean | Checkbox | TRUE |

| 11 | Notes | long_text | TEXT | string | Text | February shows two split-location weeks; the travel policy needs a decision either way. |

| 12 | Remote ID | id | SERIAL PRIMARY KEY | integer | Text (preserve source ID) | (blank) |

HQ/remote days describe the agreed weekly plan, not inferred presence. Record Core Hours Met and Approved only from an explicit verified decision; if unknown, adapt both SQL and JSON to nullable fields rather than silently treating a missing value as false. Do not infer work performance from location.

Select Options

_No Select fields._

Relations

Link fields: none

Examples

Prompt

We have remote staff across four

… (nội dung đầy đủ có trong gói tải về)