by isas1
A new four-person creative team every day, and the small web tool it built. Generated with Claude Code, recorded on GitHub.
# Add to your Claude Code skills
git clone https://github.com/isas1/daily-teamGuides for using ai agents skills like daily-team.
Last scanned: 10/8/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-10-08T11:12:39.753Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how daily-team compares with popular alternatives.
daily-team is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by isas1. A new four-person creative team every day, and the small web tool it built. Generated with Claude Code, recorded on GitHub. It has 71 GitHub stars.
Yes. daily-team passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/isas1/daily-team" and add it to your Claude Code skills directory (see the Installation section above). daily-team ships a SKILL.md manifest, so compatible agents can discover and load it automatically.
daily-team is primarily written in HTML. It is open-source under isas1 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh daily-team against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
!sh "${CLAUDE_SKILL_DIR}/team.sh"
Request: $ARGUMENTS
If the team above is missing or shows an error, run sh team.sh from this skill's folder and use its output.
Pick exactly one mode from the request. Do no more than that mode asks.
| Request | Do |
|---|---|
| Empty | Print the team and task above as written. Stop. Do not read prompt.md. |
| A brief | Write the session for the brief. Stop. Do not build. |
build, optional count 1 to 4, optional brief |
Write the session for the brief, or for today's spark if there is none. Then build that many artifacts (default 1). |
publish |
Ask the user and wait for a yes. Run exactly sh daily.sh from this skill's folder, with no flags. It records today's team and artifact with the user's Claude subscription, then commits and pushes. Report its output. |
recruit |
Ask the user and wait for a yes. Run exactly sh recruit.sh from this skill's folder, with no flags. It drafts next week's season, runs the tests, pushes a branch, and opens a pull request. Give the user the link. |
Read prompt.md in this skill's folder, sections "Work the brief" and "Writing rules", and follow them. Output the session itself, with no lead-in. Write each section heading as a level-two heading: ## Pitch, ## Clash, ## Decision or ## Deadlock, ## Build notes.
If the session ends in a Deadlock, apply the "Referee" section of prompt.md once and output its ruling. Never run a second referee.
Also read the "Build an artifact" section of prompt.md. Copy this checklist and tick it off:
Build progress:
- [ ] Session written and reviewed
- [ ] Artifact 1 written, member 1 leading, and reviewed
- [ ] Artifact n written, member n leading, and reviewed (one line per artifact)
Write artifact n to team-builds/<date>/artifact-<n>.html, relative to the working directory the user started in, not this skill's folder or a scratchpad. Write one complete file per artifact, not parts joined later. Member n leads artifact n, so each artifact takes its look and layout from a different member. Give the user the paths at the end.
Check the session and each artifact against this list. If any item fails, fix it and check again. Give the paths only when every item passes.
## Pitch, ## Clash, and then ## Decision or ## Deadlock. The Clash has 6 to 10 lines, and no member speaks more than 3 times.@import, no fetch or other network calls, and no form that posts to another site.sh and awk.publish and recruit: Claude Code, git, gh signed in, and Node 20 or later. Chrome is optional, for images.Each day, four creative roles turn current signals into one useful interactive project. GitHub Trending, Hacker News, Reddit and design/engineering feeds inform three competing directions. The team chooses a real audience, a practical need and a distinct interaction, then builds one complete offline HTML prototype.
From 2026-10-31, normal Daily Team runs focus on original projects: creative tools, simulations, games, explorable explanations and unusual product workflows. Each saved plan records its evidence, nearest familiar approach, useful difference, recovery path and comparison with recent projects. Trend signals inspire work; they do not prove demand or originality.
Component production continues separately in the private daily-components repository, copied with history before this change. Existing component-team remains separate. Earlier component days and the previously scheduled culture editions keep their original format. Explicit --pack still builds components here.
Everything in days/ is written by a language model and checked by scripts, not by hand. The model and provider for each day are on its page.
Task: Create one original, useful interactive project from current signals. Choose a real audience and need; turn cross-domain ideas into a working offline prototype.
Decision: A protocol engineer or learner hand-delivers, drops, duplicates or delays packets between two toy handshake machines while advancing the clock by hand.
Open the day · Use it · Archive
Season 5, since 2026-10-26. New this season: Interface designer, Motion director, Interaction engineer, Type designer, Accessibility specialist, Human factors engineer, Icon designer, Design systems engineer, Mobile interface designer, Data interface designer, Usability researcher, Interaction prototyper, Visual designer, Motion engineer, Interface copywriter, Quality engineer, Cabinet maker, Watch restorer, Instrument maker, Exhibit light technician, Architectural model maker, Technical illustrator, Medical illustrator, Scientific illustrator, Foley artist, Color grading specialist, Dance choreographer, Puppet maker, Stage illusion builder, Camera operator, Furniture designer, Ergonomist, Railway signaller, Control room operator, Air traffic controller, Flight deck designer, Game interface designer, Technical writer, Cartographic designer, Wayfinding designer, Precision machinist, Optical technician, Lens grinder, Instrument tuner, Kinetic sculptor, Letter cutter, Silversmith, Furniture restorer, the first 36 guests, and 24 temperaments. A new season is drafted every Monday; from 2026-10-26 it replaces 16 roles and 16 methods.
Suggest a task or vote with a thumbs-up on open suggestions. The most voted are screened every Monday.
No open suggestions yet.
| Date | Asset | Task | Team |
|---|---|---|---|
| 2026-10-31 | Handshake Bench | Color grading specialist · Wayfinding designer · Camera operator · Amber crab | |
| 2026-10-30 | Holding Panel | Dance choreographer · Railway signaller · Optical technician · Satellite repair apprentice | |
| 2026-10-29 | Brand kit import | Puppet maker · Control room operator · Foley artist · Velvet beetle | |
| 2026-10-28 | Breach Reader | Precision machinist · Air traffic controller · Furniture designer · Asteroid workshop tutor | |
| 2026-10-27 | Lit Case | Exhibit light technician · Medical illustrator · Interface designer · Impatient commuter | |
| 2026-10-26 | Bracket and Ledger | Type designer · Motion director · Motion engineer · Lunar archivist | |
| 2026-10-25 | the way back up | Window dresser · Sign painter · Textile designer · Katsushika Hokusai |
team.sh turns the date into four members, each with a role, a method, and a stance, plus a constraint and a task. For new project days the trend-backed project brief takes priority over the legacy component task pool. Open UI requests from this repo and isas1/web-components can replace the pool task; each scoped brief rests for 28 days after use, and its source is recorded. The date gives the same cast and base task; request selection depends on the saved issue snapshot and recent records. Earlier seasons used open sparks and material processes; their records stay as made. From season 3, each member also has a temperament: how they argue. Within a season no role or method repeats within 7 days and no constraint within 22 days. A pool task rests for half the task pool plus 1 days: 21 with the current 40-task pool.Suggest a task, vote with a thumbs-up on open suggestions, or read CONTRIBUTING.md.
30–31 October 2026, Lisbon time: 00:30 news/feed inspiration, 02:30 culture, 04:30 popular-component expansion. Normal 06:00 run continues. Culture continues daily afterward: a different past or present culture, without repeats, until the sourced queue ends. Twelve cultures currently queued through 10 November; the list can be extended by appending new culture IDs. News/popular stop after 31 October. Separate records preserve the normal day. Extra runs use six components plus one connected demo and skip model comparisons. Scheduled GitHub jobs may start late.
Browse extra editions · Schedule and evidence guide
Project guide covers evidence, originality checks, replay, source failure and the private component copy. Normal runs build one project (or --artifacts 0 for planning only). Use --pack for component production.
Historic