القائمة
Use when starting or completing substantive agent work that needs durable, role-labelled progress records and optional run recovery.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/MoeenNehzati/famulus --skill milestone-loggingيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use only when a generated managed-setup gate, a Famulus setup-required result, or an exact manager lifecycle route directs the agent here.
Use when the user asks to create a personal skill or change an existing personal skill's intended behavior or public interface in the shared skills directory. Do not use for behavior-preserving refactoring, blueprint regeneration, certificate work, or standards maintenance.
Install or repair an explicit subset of the optional assistant, collab, coauthor, and tw launchers.
عرض SKILL.md
| name | milestone-logging |
| description | Use when starting or completing substantive agent work that needs durable, role-labelled progress records and optional run recovery. |
Generated from
blueprint.yaml. Do not edit this block by hand.
Executable Interfaces:
Call famulus.invoke with required caller (caller skill), interface, version, and arguments; optional dry_run defaults to false. Compact uses ordered positionals plus an option mapping; ordered raw argv uses positionals: [] plus every argv token in list options. Never mix forms.
milestone-logging._rtx.interface.record — Append a role-labelled progress milestone or completion record. Progress supplies doing and optional prev; completion supplies the closing result as the done value instead of positional messages. Typed recovery state can also be mirrored into a durable run journal.
milestone-loggingmilestone
Arguments JSON (replace labels with actual values). Omit optional positionals and options that are not needed.
{"options": {"--attempt": "ATTEMPT", "--done": "PREV", "--event": "EVENT", "--evidence": "PATH", "--path": true, "--role": "ROLE", "--run": "ID", "--state": "STATE", "--step": "STEP", "--task": "TASK"}, "positionals": ["DOING", "PREV"], "stdin": null}
Required options: []; positional arity: 0..2; stdin: forbiddenmilestone-logging._rtx.interface.timeline — List milestone sessions, render one session with its transcript events, or reconstruct one durable run as text or JSON.
milestone-loggingtimeline
Arguments JSON (replace labels with actual values). Omit optional positionals and options that are not needed.
{"options": {"--json": true, "--list": true, "--run": "ID", "--slow": "SECONDS", "-l": true}, "positionals": ["SESSION"], "stdin": null}
Required options: []; positional arity: 0..1; stdin: forbiddenSkill: milestone-logging
Use record before the first substantive action, before each distinct work item, every few tool calls, and at completion. Every record is role-labelled. A progress record names the work starting now and how the preceding piece ended; a completion record closes the final work item with its outcome.
If one record invocation fails, report that exact failure once and continue the task; do not invent a record or retry blindly.
To tell the user where this session's milestones are being written, invoke milestone-logging._rtx.interface.record with only --path and report the complete returned path verbatim.
Use the durable-run mode only for work that must outlive the current session. Put recovery-relevant state in its typed fields.
For a diagnostic read, invoke timeline; use its explicit list or run route to inspect existing records.