daily-working SKILL.md skillA
daily-working from tms-tungnguyen3/daily_working is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tms-tungnguyen3/daily_working/daily-working@v2.1.0Pins v2.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tms-tungnguyen3/daily_working
- Path
skills/daily-working/SKILL.md- Versions recorded
- 7
- Latest version
- v2.1.0, committed Sep 18, 2026
- First version recorded
- Aug 22, 2026
- Size
- 7,305 bytes
- Repository stars
- 5
- License
- MIT
End-to-end pipeline: pull a task from the project's task tracker by ID (Redmine or GitHub Issues today, more addable via a new adapter), sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension (claude-in-chrome), and keep the tracker ticket in sync throughout (in-progress marker, ambiguity/impact questions, close-out comment).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# daily-working ## Purpose Coordinate a full task-to-verified-change loop without the human relaying context by hand: fetch a task from the project's task tracker (with attachments), judge whether it's actually safe and sensible to implement as understood, implement it following the target project's own conventions, verify the result in a real running browser, and close the loop back on the tracker (PR + comment + status) once that's confirmed. **Task tracker support today: Redmine and GitHub Issues.** `task_tracker` in `.claude/daily-working.yml` picks one; the pipeline itself ([phases/fetch-task](phases/fetch-task.md), [phases/close](phases/close.md), [templates/tracker-write](templates/tracker-write.md)) only ever calls a small fixed contract — `fetch`, `write_comment`, `set_status` — defined in [policies/tracker-adapter](policies/tracker-adapter.md). Each tracker's actual mechanics live in their own `adapters/<name>.md` file. Adding a third tracker means writing one new adapter file; nothing under `phases/`, `workflows/`, or `templates/` needs to change. …
Read the whole file at its exact version.
How to install
mdr add tms-tungnguyen3/daily_working/daily-working@sha256:254243194866bd30The line at the top of this page pins the label v2.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kl52ycitl6fqz3m7)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Aug 22, 2026 and Sep 18, 2026, about one every 4 days. Its first recorded version is graded B and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.0 latest | 2026-09-18 | 24e0ed0 | 7,305 B | A | view · diff |
| v2.0.1 | 2026-09-10 | 78901fe | 6,906 B | A | view · diff |
| v2.0.0 | 2026-09-09 | bc6264b | 6,906 B | A | view · diff |
| v1.7.0 | 2026-08-25 | 9f0b119 | 29,502 B | B | view · diff |
| v1.6.0 | 2026-08-22 | e49b61f | 25,093 B | B | view · diff |
| v1.5.0 | 2026-08-22 | f57c771 | 24,293 B | B | view · diff |
| v1.4.0 | 2026-08-22 | ef5011d | 19,669 B | B | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7305 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tms-tungnguyen3/daily_working · 5 stars · license MIT · pushed 2026-09-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kl52ycitl6fqz3m7 GET https://markdownregistry.com/api/v1/resolve?ref=tms-tungnguyen3/daily_working/daily-working GET https://markdownregistry.com/api/v1/blob/254243194866bd3030770cf0775ac758f20a7bce2dbc964a0c62bb7f7d2a8fbf
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.