[dogfood][cursor,windsurf][main] adapters/INDEX.md skill counts stale (cursor 181 vs 180; windsurf 176 vs 148)

Open Beginner friendly
#214 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, shell
Domain
tooling

Research direction

Start with adapters/INDEX.md and install.sh. Run HOME=$H bash install.sh --adapter for cursor and windsurf, then count the delivered skills/ entries and compare them with the table and shortfall row. Done means the documented counts agree with the plain-run results and no contradictory windsurf values remain.

Written by the indexing model from the issue text.

Description

dogfood P2

Adapter: cursor, windsurf
Install path: main 829f516 (npm 1.5.0: cursor 180, windsurf 175)

Exact command: HOME=$H bash install.sh --adapter <x>, then count skills/

Expected: Delivered skill counts match adapters/INDEX.md (cursor 180, windsurf 148 plain run).

Actual: On main, cursor delivers 181 skills (installer prints Skills : 181) and windsurf delivers 176. INDEX.md wasn't regenerated after #183. It also contradicts itself for windsurf: the table row says 148, and the shortfall row says 175 | 148 | -27.

Output

main cursor:   Skills : 181 ; skills: 181
main windsurf: skills: 176
adapters/INDEX.md:16 | `cursor` | 386 | 342 | 180 | 0 | — | 0 |
adapters/INDEX.md:25 | `windsurf` | 0 | 0 | 148 | 35 | — | 0 |
adapters/INDEX.md:81 | `windsurf` | 175 | 148 | -27 |

Found by: Simay (SI dogfood 2026-09-24). Isolated HOME under /workspace/si-dogfood/simay/home/; raw logs in /workspace/si-dogfood/simay/logs/.

Dominant language
HTML
Stars
347
Forks
12
Avg merge
2d 16h
Merged PRs (30d)
95

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coco-research/coco

All issues in coco-research/coco

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.