chore(skills): sync vendored dailybot skill pack to v3.10.3 - #72
Merged
Conversation
## Summary Dogfood sync of .agents/skills/dailybot/ to the freshly released DailybotHQ/agent-skill v3.10.3, which documents the real kudos wall-of-fame JSON payload shape (nested user names, paginated leaderboard envelope, caller position) and pins the human-rendering fix to dailybot-cli v3.7.2. ## Change Log - Sync all vendored SKILL.md files to v3.10.3 (frontmatter bump + the new wall-of-fame payload reference in kudos/SKILL.md) - Recover the env sub-skill: the broad `env/` gitignore rule (meant for Python virtualenvs) was silently swallowing .agents/skills/dailybot/env/, so it was never committed even though AGENTS.md and the catalog reference /dailybot-env. Virtualenv ignore patterns are now anchored to the repo root (/env/, /venv/, /.venv/) and the sub-skill is vendored for the first time - Bump the pack version reference in AGENTS.md and .agents/docs/skills_agents_catalog.md to v3.10.3 - docker/local/cli: raise the dev-container CLI floor to >=3.7.2 (the release that fixed the wall-of-fame rendering) ## Risks - None at runtime — vendored docs + local dev tooling only; no source or packaging changes. Anchoring the virtualenv ignore patterns only affects developers with a nested env/ virtualenv (unconventional) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Merge with
[skip release]in the squash-commit body (per AGENTS.md § 15.a — this PR is the one sanctioned use case: a dogfood sync of the vendored skill pack). In the GitHub merge dialog, add the literal line[skip release]to the commit body, or merge with:Rationale: the pack pins
dailybot-cli >= 3.7.0; releasing the CLI on this sync would advance it past the floor the fresh pack references and re-enter the sync loop.Summary
Syncs
.agents/skills/dailybot/to DailybotHQ/agent-skill v3.10.3, which documents the real kudos wall-of-fame JSON payload shape (agent-skill#40) and pins the human-rendering fix todailybot-cliv3.7.2 (#71).Changes
kudos/SKILL.md(nesteduser.full_name,leaderboard.resultsenvelope,leaderboard_summary= caller position, version note pinned to the shipped v3.7.2 release).envsub-skill 🔎: the broadenv/gitignore rule (meant for Python virtualenvs) was silently swallowing.agents/skills/dailybot/env/, so previous syncs (including docs(readme,skills): 3.7.0 as the documented baseline + sync vendored skill pack to v3.10.2 #70) never actually committed it — even thoughAGENTS.mdand the skills catalog reference/dailybot-env. The virtualenv ignore patterns are now anchored to the repo root (/env/,/venv/,/.venv/) and the sub-skill lands in the repo for the first time.AGENTS.mdand.agents/docs/skills_agents_catalog.mdnow say v3.10.3.docker/local/cli/Dockerfileraises the CLI floor to>=3.7.2(the release that fixed the wall-of-fame rendering) — rides along per explicit maintainer request; local dev tooling only, not shipped.Risks
None at runtime — vendored docs + local dev tooling only; no source or packaging changes. The anchored ignore patterns only affect a developer who keeps a virtualenv in a nested
env/directory (unconventional; root-level virtualenvs stay ignored).🤖 Generated with Claude Code