chore: Refresh the kit: TASKS.md ledger, media names and format links
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- json, markdown
- Domain
- content, documentation
Research direction
Start at the repo root and read AGENTS.md, CLAUDE.md, package.json, and the existing projects/, agents/, automations/, and apps/ folders. Create projects/TASKS.md with Done and Knowledge sections plus media/README.md naming files as agents see them, then update manifest.json and each folder to link to and validate against the public format descriptions. Remove the tool counts, replace package-count wording with "100+ integrations", and check package.json dependencies. Done means the new files exist, JSON validates, and no stale counts remain.
Written by the indexing model from the issue text.
Description
This kit is the template that people clone to learn the shape of a workspace. Three parts of it are older than the product.
| # | What changed in Taskade | What the kit needs |
|---|---|---|
| 1 | Taskade EVE keeps a TASKS.md ledger in a workspace, with a Done section and a Knowledge section |
An example projects/TASKS.md with the two sections, so a clone shows what Taskade EVE writes |
| 2 | The media browser is named Media Files, with Browse Computer for uploads. Agents read the folders | A media/README.md: name each file the way an agent sees it |
| 3 | The bundle format has a public description for each part (bundle, project, automation, agent, app) | manifest.json and each of projects/, agents/, automations/ and apps/ link to the matching description and validate against it |
Also to check: tool counts in AGENTS.md and CLAUDE.md (remove each count), the wording "100+ integrations" in place of a package count, and the dependencies in package.json.
Effort: small. One pull request, content of this repository only.
BEFORE AFTER
clone kit -> projects/ agents/ flows/ clone kit -> same, plus:
projects/TASKS.md (ledger shape)
media/README.md (names that agents read)
manifest.json -> format links + validation
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 30m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from taskade/taskade-sample-app
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
All issues in taskade/taskade-sample-app
Similar issues
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area/dashboard kind/bug QA/dev-automation
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#13939 ·
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day