メニュー
Upload a locally drafted task to the ERP via API. Use when user says "upload task", "add task", "task-add", "push task", or "submit task draft".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | task-add |
| description | Upload a locally drafted task to the ERP via API. Use when user says "upload task", "add task", "task-add", "push task", or "submit task draft". |
| disable-model-invocation | true |
Upload a locally drafted task to the ERP via API.
This command takes no arguments. It reads from draft files in data/tasks/.
Auth token is loaded from the WEBAPP_ACCESS_TOKEN variable — first from .env in the current working directory, then from ~/.claude/.env as a global fallback.
Load the auth token by reading .env in the current working directory and extracting the WEBAPP_ACCESS_TOKEN value. If the variable is missing or empty, try ~/.claude/.env as a fallback. If still missing in both locations, tell the user to set it in either .env (project-level) or ~/.claude/.env (global) and stop.
Scan data/tasks/ for .md files that contain task drafts (files with a # title line and metadata like Priority, Status, etc.).
/task-draft first and stop.Read the selected .md draft file and extract:
# <title> heading- **Priority**: <value>- **Status**: <value>- **Start date**: <value>- **Project ID**: <value> (use null if "None")## Description headingDisplay the parsed task and ask the user to confirm before uploading:
Ready to create task:
Title: <title>
Priority: <priority>
Status: <status>
Start date: <start_date>
Project: <project title or "None">
Proceed?
curl -s -X POST "https://api-erp.tadreamk.com/api/v1/tasks/" \
-H "Authorization: Bearer <token>" \
-H "Content-Type: application/json" \
-d @data/tasks/tmp_create.json
Build the request body as a temporary JSON file data/tasks/tmp_create.json:
{
"title": "<title>",
"description": "<description>",
"priority": "<priority>",
"status": "<status>",
"start_date": "<start_date>",
"project_id": "<project_id or null>"
}
Use a temporary file and curl -d @file to avoid shell escaping issues. Delete the temp file after use.
Parse the response. If creation fails, display the error and stop.
Task created successfully!
Slug: <slug>
Title: <title>
Priority: <priority>
Status: <status>
Project: <project title or "None">
URL: https://erp.tadreamk.com/tasks/<slug>
Generate a Gemini text-to-speech audio file for each narrative-style .md file in a directory tree, and attach a Listen link at the top of every file. Strips ASCII diagrams, navigation, and separators before synthesis — only paragraph prose is spoken. Use when user says "generate story audio", "text to speech for stories", "tts for markdown", "attach audio to stories", or "local-audio".
End-to-end ERP marketing article workflow — fetch today's marketing task, write the article with diagram and translations, upload to production, and mark the task as completed. Use when user says "marketing article", "erp marketing", "write today's marketing article", or "local-erp-marketing-article".
Assign the next 5 unchecked ERP features from data/erp_features.md as ERP Marketing tasks, distributed one per weekday (Mon–Fri) of the coming week. Use when user says "weekly assignment", "assign marketing tasks", "erp marketing weekly", or "local-erp-marketing-article-weekly-assignment".
Bulk-like posts on the TadReamk LinkedIn company page feed. Navigates to the admin feed, injects a JS script that likes posts with random delays, scrolls to load more, and monitors until the target count is reached. Use when user says "linkedin like", "like linkedin posts", "bulk like", or "local-erp-marketing-linkedin-like".
Generate a narrative user-story documentation set from a customer-requirement share URL. Fetches the document, saves it under data/customer_requirements/ as requirements.md (or requirements_cn.md + requirements_en.md if Chinese), then turns each feature into a human-centred, diagram-driven chapter under narrative_user_story/. Use when user says "generate narrative user story", "write narrative user story", "narrative story from requirements", "narrative docs", or "local-generate-narrative-user-story".
Sync the local .claude.prod/api_doc/ directory with the latest API documentation from the fullstack ERP project. Use when user says "update api doc", "sync api doc", "refresh api doc", or "api-doc-update".