Agent skill

Myagents Task Automation

by hAcKlyc in hAcKlyc/MyAgents

让 Agent 建立 MyAgents Task 的完整产品心智模型,并创建、验证和治理需要持久追踪、独立 Session 或未来触发的工作:理解 Task 与立即执行/Record/Goal 的边界,以及 once/scheduled/recurring、Session routing、结束条件和 command Detector。用户提到创建…

AGPL-3.0Auto-check passedProductivity & Automation

Install Myagents Task Automation

skills CLI
$ npx skills add hAcKlyc/MyAgents --skill myagents-task-automation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hAcKlyc/MyAgents myagents-task-automation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hAcKlyc/MyAgents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/bundled-skills/myagents-task-automation .claude/skills/myagents-task-automation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
myagents-task-automation
GitHub stars
915
Token cost
~1.9k tokens
SKILL.md length
485 words
Files
2 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
AGPL-3.0

At a glance

让 Agent 建立 MyAgents Task 的完整产品心智模型,并创建、验证和治理需要持久追踪、独立 Session 或未来触发的工作:理解 Task 与立即执行/Record/Goal 的边界,以及 once/scheduled/recurring、Session routing、结束条件和 command Detector。用户提到创建…

  • Works in 5 steps: 行动:命中时 AI 具体做什么。把它写进 task.md;Detector… → 时间:选择未来某时执行一次、固定间隔或 Cron 表达式。墙钟时间默认使用本机… → 激活策略:按上表选择 always 或 command… → …
  • Tasks that involve Workflow automation
  • SKILL.md covers 先建立 Task 产品心智模型, 选择激活方式, 决策顺序 and always:到点直接激活, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Myagents Task Automation is an agent skill from hAcKlyc/MyAgents. 让 Agent 建立 MyAgents Task 的完整产品心智模型,并创建、验证和治理需要持久追踪、独立 Session 或未来触发的工作:理解 Task 与立即执行/Record/Goal 的边界,以及 once/scheduled/recurring、Session routing、结束条件和 command Detector。用户提到创建 Task、定时、稍后、周期检查、持续关注、满足条件才处理时使用;普通立即执行、仅保存 Record 或明确要求 Goal Mode 的工作不使用。

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/command-detector.md`).

It sits in Productivity & Automation, covering Workflow automation. The repository describes itself as: MyAgents - 优雅、易用的 Agent 桌面端 ,一站式 Agent 工作台与任务中心. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Workflow automation

Example prompts

  • “/myagents-task-automation”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. 行动:命中时 AI 具体做什么。把它写进 task.md;Detector 的输出只能提供事件证据,不能代替行动目标。
  2. 时间:选择未来某时执行一次、固定间隔或 Cron 表达式。墙钟时间默认使用本机 IANA 时区;用户指定其他时区时显式保存。
  3. 激活策略:按上表选择 always 或 command Detector。只向用户澄清实际效果,不要求用户理解这两个内部名称。
  4. Session:延续当前/已有上下文用 single-session;每次需要隔离上下文用 new-session。
  5. 结束:一次性任务自然结束;循环任务根据用户意图选择最大 AI 执行次数、截止时间、允许 AI 主动退出,或持续到用户暂停。Detector 的 quiet 检查不计入 AI 执行次数。

What it can do on your machine

Read from SKILL.md and the folder at commit f873ca3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Myagents Task Automation loads about 1.9k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 485 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hAcKlyc/MyAgents at commit f873ca3, republished under its AGPL-3.0 licence (© hAcKlyc). 485 words, ~1,937 tokens.

Download SKILL.mdSave it as .claude/skills/myagents-task-automation/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
myagents-task-automation
description
让 Agent 建立 MyAgents Task 的完整产品心智模型,并创建、验证和治理需要持久追踪、独立 Session 或未来触发的工作:理解 Task 与立即执行/Record/Goal 的边界,以及 once/scheduled/recurring、Session routing、结束条件和 command Detector。用户提到创建 Task、定时、稍后、周期检查、持续关注、满足条件才处理时使用;普通立即执行、仅保存 Record 或明确要求 Goal Mode 的工作不使用。
metadata.author
MyAgents

MyAgents Task 与自动化

先建立 Task 产品心智模型

Task 是 MyAgents 对“需要在当前对话之后继续存在、在未来被执行和追踪的工作”的统一承载。它不是一条临时提醒,也不是一段 Cron 表达式;它把用户的行动目标保存成有身份、有状态、有执行记录、可暂停和可恢复的工作项,并在合适的时机把工作交给 AI。

一个自动化 Task 由五个彼此独立的决策组成:

text
Task = action(AI 被激活后做什么,权威内容在 task.md)
     + schedule(何时产生一次执行机会)
     + activation(机会出现时是否真的唤醒 AI)
     + Session routing(在哪段上下文中工作)
     + end conditions(何时不再继续)

schedule 只负责产生执行机会,不等于 AI 已经运行;activation 再决定这个机会是直接进入 AI Turn,还是先由程序筛选。这样,普通定时任务与“持续检查、命中才处理”共享同一个 Task 生命周期,而不需要两套产品实体。

Task 解决四类问题:

  • 意图持久化:工作不依赖当前聊天回合继续存在,之后仍可查到目标、配置和状态。
  • 未来触发:支持指定时间一次、固定间隔和 Cron 墙钟计划。
  • 按需唤醒:既能每次到点都运行 AI,也能先做低成本确定性检查,避免无意义的模型调用。
  • 治理与追踪:统一管理 Session 去向、运行历史、暂停/恢复、结束条件和失败健康状态。
与相邻能力的边界
用户真正需要的是什么正确承载
现在就在当前回合完成一件事直接执行,不创建 Task
先保存一条文字或音频记录,暂时不执行Record
一项已经明确、需要未来触发或持续追踪的工作Task
当前 Session 围绕同一目标连续多轮自主推进Goal Mode,不用循环 Task 模拟
App 完全退出后仍必须由 OS 常驻执行不属于 MyAgents Task;不要伪装成已部署成功

Cron 只是已发布的兼容命令面,不是另一种资源;Sensor 也不是独立产品实体。TaskStore 是唯一权威,新 Agent 工作流统一使用 myagents task ...。

生命周期应怎样理解

创建 Task 只是把它持久化为 Todo;首次 run 后,时间型 Task 进入 Running,表示 scheduler 已启用,不表示 AI 此刻正在执行。每个 tick 经 activation 后才可能产生 AI Turn。首次 tick 由 schedule 决定:固定 interval 默认在 run 后约 2 秒产生第一次机会(要延后就显式设置 --startAt),Cron 等到下一个墙钟点,scheduled 等到 dispatchAt。stop 暂停未来调度并停止活跃执行;start 按保留的 schedule anchor 恢复,anchor 已过期时下一次机会可能接近当前时间,应以回执里的 nextExecutionAt 为准。rerun 重新派发终态 Task;run-now 是一次绕过 Detector 的人工执行,不改变 schedule 或 checkpoint。

MyAgents App 必须在线才会产生 tick 或执行检查。Task 可以在 App 后台驻留时运行,但完全退出或 OS 休眠期间不会运行,也不会逐个补跑错过的 tick。

正常创建和列表会自动继承当前 MyAgents workspace,不需要先查 ID。只有明确跨 workspace 操作时才同时传 --workspaceId / --workspacePath;若要诊断当前身份,使用 myagents agent current --json。命令语法有疑问时运行 myagents task readme 获取当前紧凑契约;精确参数以对应命令的 leaf help 为准。

选择激活方式

方式每个 schedule tick 的效果适用情况Task 配置
always直接派发普通 Task AI Turn;没有前置程序判断每次到点都值得让 AI 行动,例如提醒、日报、定期总结;或是否行动只能由模型理解省略 --trigger-file
command DetectorMyAgents harness 先运行本地命令;quiet 不创建 Session、不唤醒 AI,activate 才把事件证据交给普通 Task AI Turn外部条件能由廉价、确定的程序判断,而且大多数检查应该保持静默验证后传 --trigger-file

默认选择 always。只有“程序可以可靠判断是否命中”“运行程序明显比唤醒 AI 更便宜”“未命中时不需要 AI 参与”同时成立,才使用 command Detector。不要创建一个脚本,再让脚本无条件输出 activate;那与 always 等价,只增加故障点。

一旦选择 command Detector,在编写脚本或 Trigger 前完整读取 references/command-detector.md。该 reference 是命令结构、stdin/stdout 协议、checkpoint、fixture 测试、安全边界和 failure 行为的详细契约;普通 always Task 不需要加载它。

决策顺序

  1. 行动:命中时 AI 具体做什么。把它写进 task.md;Detector 的输出只能提供事件证据,不能代替行动目标。
  2. 时间:选择未来某时执行一次、固定间隔或 Cron 表达式。墙钟时间默认使用本机 IANA 时区;用户指定其他时区时显式保存。
  3. 激活策略:按上表选择 always 或 command Detector。只向用户澄清实际效果,不要求用户理解这两个内部名称。
  4. Session:延续当前/已有上下文用 single-session;每次需要隔离上下文用 new-session。
  5. 结束:一次性任务自然结束;循环任务根据用户意图选择最大 AI 执行次数、截止时间、允许 AI 主动退出,或持续到用户暂停。Detector 的 quiet 检查不计入 AI 执行次数。

只澄清会改变这些选择的缺失信息。普通的明确创建请求在信息齐全后连续完成准备、验证、创建、回读和启动,不逐步索要批准;删除仍遵守 /myagents-cli 的确认规则。若本轮来自 <TASK_DISCUSSION>,则由 myagents-task-alignment 负责候选文档与创建前确认,必须等用户明确确认后才 mutation。

always:到点直接激活

先用标准文件工具写 task-action.md,再创建 Task。长文本不要拼进 shell command。

未来某时执行一次:

bash
myagents task create-direct --name "send release reminder" \
  --taskMdFile task-action.md --executionMode scheduled \
  --dispatchAt 2026-08-04T09:00:00+08:00 \
  --runMode single-session --preselectedSessionId current --json

周期执行:

bash
myagents task create-direct --name "daily report" \
  --taskMdFile task-action.md --executionMode recurring \
  --cronExpression "0 9 * * *" --cronTimezone Asia/Shanghai \
  --runMode new-session --json

固定间隔使用 --intervalMinutes <n>(最小 5 分钟)。默认首次 tick 在 run 后约 2 秒;如果用户希望“从一个 interval 之后才第一次检查”,同时传带时区的 --startAt <ISO-8601>。普通 Task 省略 --trigger-file,其有效激活策略就是 always。

command Detector:命中才激活

只有在上面的三个条件都成立后才进入本节。完整读取 references/command-detector.md,再编写脚本、隔离测试输入并部署;不要凭本文件的摘要猜协议。

条件 Task 与普通 Task 只有一个创建差异:验证通过后在 create-direct 加入生产用 --trigger-file。例如:

bash
myagents task create-direct --name "watch CI failure" \
  --taskMdFile task-action.md --executionMode recurring --intervalMinutes 5 \
  --runMode single-session --preselectedSessionId current \
  --maxExecutions 1 --trigger-file trigger.production.json --json

这里的 --maxExecutions 1 表示首次 activate 并完成 AI Turn 后结束;之前任意数量的 quiet 检查不消耗次数。需要持续观察后续事件时省略它。

Show full SKILL.md (186 more words)Show less

结束条件

创建 ordinary scheduled/recurring Task 时可组合:

text
--deadline <ISO-8601-with-offset>  到达该时刻后不再开始新 AI Turn
--maxExecutions <positive-int>     限制已结算的 AI 执行次数
--aiCanExit true|false             是否允许任务内 AI 主动结束

当 --aiCanExit true 且行动已经完成、继续运行无意义时,Task 内的 AI 可以调用:

bash
myagents task exit --reason "goal achieved: ..."

它不是临时失败的逃生按钮。瞬时错误应按 task.md 的处理策略重试或报告;不要擅自结束用户仍需要的周期任务。

创建后的确定性流程

创建命令始终加 --json,从结果解析权威 taskId,然后回读并启用:

bash
myagents task get <taskId> --json
myagents task run <taskId> --json

创建、get、run、rerun 的 JSON 结果都提供固定的 data.receipt:从这里读取 taskId、status、statusMeaning、changed、nextExecutionAt、瞬时 executionState 和 resultAccess,不要猜测不同命令的旧字段层级。Running 只表示 scheduler enabled;重复或并发 task run 已经 Running 的 Task 会成功返回 changed: false,不会创建第二次派发,也不应重试。start、stop 的既有回执仍包含权威状态与 nextExecutionAt。首次从 Todo 启用用 task run;暂停后恢复用 task start;终态重新派发用 task rerun。不要通过目录时间或猜测名称寻找刚创建的 Task。

resultAccess 只解释现有结果通道:single-session 的结果留在绑定 Session;new-session 的结果留在各次执行 Session 和 task runs 历史。系统不会把执行结果自动推回创建 Task 的 Session,也不会把普通 assistant 输出自动复制为 Task 评论;需要沉淀到本地时间线时由 Agent 显式调用 task comment。

治理

bash
myagents task get <taskId> --json       # 权威配置、状态、Detector health/checkpoint
myagents task runs <taskId> --limit 5 --full --json # 最近 AI 执行历史与结果正文
myagents task check-now <taskId>        # 真实 Detector 检查;提交状态,命中会激活 AI
myagents task run-now <taskId>          # 绕过 Detector,直接执行 AI
myagents task stop <taskId>             # 暂停 schedule,保留 checkpoint
myagents task start <taskId>            # 按原 anchor 恢复;查看回执 nextExecutionAt
myagents task reset-checkpoint <taskId> # 只清平台 checkpoint
myagents task update <taskId> --clear-trigger # 改回 always
myagents task archive <taskId>           # 用户专属的长期可恢复归档
myagents task delete <taskId>            # 在对话中先取得用户确认,再执行;CLI 不弹窗

check-now 会提交真实 MyAgents 状态;部署前不提交 MyAgents 状态的验证使用 trigger test(脚本自身副作用仍真实发生)。run-now 不改变 schedule anchor 或 Detector checkpoint。

归档和删除不是同一种“软删除”:archive 是长期可恢复的产品状态;delete 会立即停止调度、移除平台 Trigger state/pending activation,并从正常产品使用中不可恢复地移除 Task。TaskStore 只保留防止旧 Cron 重新迁移所需的内部 tombstone 与审计;没有 30 天恢复承诺,也没有 undelete 命令。两者都不会越权清理工作区脚本、脚本数据库或外部状态。

本地 Task 评论

Task 可以作为跨 Session 的本地协作中枢。需要回看时间线时用 myagents task comments <taskId> --json。只有当结果、风险、经验或待用户决策的信息确实值得沉淀到 Task 时,Agent 才显式调用:

bash
myagents task comment <taskId> --body-file result.md --json

在 Task 自身触发的执行 turn 内可省略 <taskId>;在用户评论注入的后续 turn 中,必须使用隐藏提醒提供的显式 Task ID。

回复某条评论时增加 --reply-to <commentId>。长文本始终先写文件,不把多行正文拼进 shell。普通 assistant 回复不会自动登记为 Task 评论;从本地 Task 评论收到的 query 应服从该轮 TASK_COMMENT reminder,而从 Space Issue Delivery 收到的 query 继续使用 Cloud Issue 的回复命令,二者不得默认双写。

给用户的部署回执

部署成功后一次说明:

  • Task 名称与 ID
  • 何时执行或检查,包括时区
  • 到点直接激活,还是满足什么程序条件才激活
  • 激活后的 AI 动作
  • 目标 Session 策略
  • 结束条件或“持续到手动停止”
  • App 在线限制和 Task Center 治理入口

quiet 检查保持静默。activate 后由目标 Session 中的 AI 正常交付工作结果;Detector failure 只进入 Task health/backoff,不伪装成业务判断,也不再创建一个 AI Task 去监控 Detector。

© hAcKlyc, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in bundled-skills/myagents-task-automation of hAcKlyc/MyAgents.

  • SKILL.md
  • references/command-detector.md

Open the folder on GitHubat commit f873ca3

Compare with similar skills

Myagents Task Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Myagents Task Automation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Myagents Task Automation this skillhAcKlyc/MyAgents915—~1.9kAutomated safety check: PassAGPL-3.0
Newsblur CLIsamuelclay/NewsBlur7.6k—~1.3kAutomated safety check: PassMIT
Robocorp Automationrobocorp/robocorp653—~2.4kAutomated safety check: PassApache-2.0
Connect Apps with ComposioComposioHQ/awesome-claude-skills77k3 repos~557Automated safety check: PassNone
Zapier SDKzapier/sdk262—~2.9kAutomated safety check: PassMIT
Zapier Demozapier/zapier-mcp428—~2.7kAutomated safety check: PassMIT

Similar skills

  • Newsblur CLI

    samuelclay/NewsBlur

    Manage your NewsBlur from the terminal. An agent skill from samuelclay/NewsBlur.

    7.6k GitHub stars~1.3k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Robocorp Automation

    robocorp/robocorp

    Bootstrap from an empty folder or build, debug, locally run, and validate Python automations built with Robocorp or Sema4.ai tooling, robocorp.tasks, rcc, robocorp-browser, and RPA Framework.

    653 GitHub stars~2.4k tokensUpdated 6 days ago
    Productivity & AutomationAuto-check passed
  • Connect Apps with Composio

    ComposioHQ/awesome-claude-skills

    Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.

    77k GitHub starsUsed in 3 repos~557 tokens
    Productivity & AutomationAuto-check passed
  • Zapier SDK

    zapier/sdk

    Official

    Zapier SDK for TypeScript. An agent skill from zapier/sdk.

    262 GitHub stars~2.9k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed
  • Zapier Demo

    zapier/zapier-mcp

    Official

    Walk a new user through setting up their first Zapier action and running it live — the smallest possible win.

    428 GitHub stars~2.7k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed
  • Just

    disler/bowser

    Use just to save and run project-specific commands. An agent skill from disler/bowser.

    265 GitHub stars~792 tokensUpdated 7 mo ago
    Productivity & AutomationAuto-check: notes

More from hAcKlyc/MyAgents

All 15 skills in this repo
  • Hatch Pet

    hAcKlyc/MyAgents

    Create, repair, validate, visually QA, and package MyAgents/Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual…

    915 GitHub starsUsed in 1 repo~9.5k tokens
    Auto-check passed
  • Download Anything

    hAcKlyc/MyAgents

    Find and download virtually any digital resource from the internet — ebooks, academic papers, movies, TV shows, music, software, images, fonts, courses, and more.

    915 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Myagents Memory Gardener

    hAcKlyc/MyAgents

    仅当系统或用户明确指定完整名称 myagents-memory-gardener 时使用; 不要根据任务语义或相似表述自行触发。

    915 GitHub stars~425 tokensUpdated today
    Auto-check passed
  • Myagents Memory Molt

    hAcKlyc/MyAgents

    仅当系统或用户明确指定完整名称 myagents-memory-molt 时使用; 不要根据任务语义或相似表述自行触发。

    915 GitHub stars~546 tokensUpdated today
    Auto-check passed
  • Support

    hAcKlyc/MyAgents

    MyAgents 本地问题诊断、恢复与反馈升级流程。用户描述报错、崩溃、无响应、配置后仍不可用、状态或结果不符合预期、 Task/Goal/Channel/Provider/Runtime/MCP/Plugin/附件/Agent 网络/协作空间等功能异常,或者前端“小助理诊断/问题反馈”注入诊断上下文时使用。

    915 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Prompt Writer

    hAcKlyc/MyAgents

    Methodology for writing or improving prompts and system prompts that drive any LLM.

    915 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Questions about Myagents Task Automation

What does Myagents Task Automation do?

让 Agent 建立 MyAgents Task 的完整产品心智模型,并创建、验证和治理需要持久追踪、独立 Session 或未来触发的工作:理解 Task 与立即执行/Record/Goal 的边界,以及 once/scheduled/recurring、Session routing、结束条件和 command Detector。用户提到创建…. Myagents Task Automation is an agent skill from hAcKlyc/MyAgents.

When should I use Myagents Task Automation?

Myagents Task Automation fits situations like: tasks that involve Workflow automation.

How do I install Myagents Task Automation in Claude Code?

Run `npx skills add hAcKlyc/MyAgents --skill myagents-task-automation -a claude-code`. Or copy the skill folder (bundled-skills/myagents-task-automation in hAcKlyc/MyAgents) into .claude/skills/myagents-task-automation in your project. Claude Code loads it when a task matches its description.

How do I install Myagents Task Automation in Codex?

Run `npx skills add hAcKlyc/MyAgents --skill myagents-task-automation -a codex`. Or copy the skill folder (bundled-skills/myagents-task-automation in hAcKlyc/MyAgents) into .agents/skills/myagents-task-automation in your project. Codex loads it when a task matches its description.

Can I use Myagents Task Automation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hAcKlyc/MyAgents --skill myagents-task-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/myagents-task-automation, .gemini/skills/myagents-task-automation, .github/skills/myagents-task-automation and .opencode/skills/myagents-task-automation in your project.

What does Myagents Task Automation need to run?

SKILL.md names no scripts, command-line tools or credentials: Myagents Task Automation is instructions for the agent only.

Does Myagents Task Automation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Myagents Task Automation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Myagents Task Automation use?

Myagents Task Automation is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Myagents Task Automation use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Myagents Task Automation?

Skills that share tags, products or a category with Myagents Task Automation: Newsblur CLI (samuelclay/NewsBlur, 7.6k stars), Robocorp Automation (robocorp/robocorp, 653 stars), Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars) and Zapier SDK (zapier/sdk, 262 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Myagents Task Automation?

hAcKlyc (a GitHub user) maintains it in hAcKlyc/MyAgents, which has 915 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: hAcKlyc/MyAgents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.