当前时间: 2026-06-04 08:21:39
分类:办公文件
评论(0)
当健身APP也开始搞Skill我一周撸铁4-5次,用某APP记录差不多小半年了。就一个纯工具,记记组数重量,够用。直到前几天我在里面翻到一个功能——数据导出供外部Agent调用。我上班天天跟AI打交道,怎么健身APP里也冒出来了?第一反应以为APP内置了个AI助手,那种对话框帮你分析训练数据的。但转念一想,这APP是买断制的,一次付费终身用。要是内置AI,token费用谁扛?用户越多亏越多,不现实。果然,仔细看了下不是内置AI,而是开放了Skill让你接自己的Agent。你可以把训练数据喂给Claude或Codex这类Agent,让它分析你的训练情况、薄弱肌群、训练量够不够。反过来也行,让Agent生成训练计划,直接通过Skill写回APP,不用一个动作一个动作手动添加。想法挺好,但这功能要会员。我自己没开——会员最大的价值是动作指引和发力标准,我有点基础用不太上,就借了朋友的会员试了试。最明显的:Agent生成的动作名称跟APP数据库里的不能完全对应上,名称不匹配直接导入报错。得手动改名才能同步,挺破坏体验的。还有就是动作数量超过限制后同步直接出问题,计划安排多了后面的就写不进去。所以目前更像是个"概念先行"的阶段——方向对,打磨还不够。普通用户不用专门为这个开会员。但如果你本身就用Agent,可以关注后续更新。不过从技术视角看,健身APP提供Skill这个思路挺聪明的。不自己烧token做AI功能,把接口开放出来让用户接自己的Agent,成本直接转移给用户了。以后大概率会有更多工具类APP走这条路。
基本
文件
流程
错误
SQL
调试
- 请求信息 : 2026-06-04 09:46:22 HTTP/1.1 GET : https://www.yeyulingfeng.com/a/708975.html
- 运行时间 : 0.252908s [ 吞吐率:3.95req/s ] 内存消耗:4,681.81kb 文件加载:145
- 缓存信息 : 0 reads,0 writes
- 会话信息 : SESSION_ID=641cfd7dfa92e2b9d2ab3984f498a96e
- CONNECT:[ UseTime:0.000934s ] mysql:host=127.0.0.1;port=3306;dbname=wenku;charset=utf8mb4
- SHOW FULL COLUMNS FROM `fenlei` [ RunTime:0.001147s ]
- SELECT * FROM `fenlei` WHERE `fid` = 0 [ RunTime:0.000452s ]
- SELECT * FROM `fenlei` WHERE `fid` = 63 [ RunTime:0.000412s ]
- SHOW FULL COLUMNS FROM `set` [ RunTime:0.000792s ]
- SELECT * FROM `set` [ RunTime:0.000375s ]
- SHOW FULL COLUMNS FROM `article` [ RunTime:0.000888s ]
- SELECT * FROM `article` WHERE `id` = 708975 LIMIT 1 [ RunTime:0.007188s ]
- UPDATE `article` SET `lasttime` = 1780537582 WHERE `id` = 708975 [ RunTime:0.075613s ]
- SELECT * FROM `fenlei` WHERE `id` = 64 LIMIT 1 [ RunTime:0.001546s ]
- SELECT * FROM `article` WHERE `id` < 708975 ORDER BY `id` DESC LIMIT 1 [ RunTime:0.001039s ]
- SELECT * FROM `article` WHERE `id` > 708975 ORDER BY `id` ASC LIMIT 1 [ RunTime:0.027794s ]
- SELECT * FROM `article` WHERE `id` < 708975 ORDER BY `id` DESC LIMIT 10 [ RunTime:0.012432s ]
- SELECT * FROM `article` WHERE `id` < 708975 ORDER BY `id` DESC LIMIT 10,10 [ RunTime:0.019953s ]
- SELECT * FROM `article` WHERE `id` < 708975 ORDER BY `id` DESC LIMIT 20,10 [ RunTime:0.004116s ]
0.254735s