cwork101 / contribute
Corrections and submissions
This reference is only as good as its worst out-of-date page. Telling it what changed is the single most useful thing you can do.
Something is wrong
A price, a limit, an availability claim or a date that no longer matches reality. Include the page and, if you have one, a link to the source that contradicts it.
Page URL · what is wrong · a source link
Something is missing
A product, feature, model or course with no entry yet. Ecosystem entries need enough detail to fill the directory record.
Name · official link · why it matters
A project to list
MCP servers, Agent Skills, plugins, connectors and tools. Community projects are always labelled as such, and listing is never an endorsement.
Repository · maintainer · licence · what it works with
What makes a submission easy to act on
- A link beats a description. One official URL settles most questions instantly.
- Say when you saw it. Availability changes constantly; a dated observation is far more useful than an undated one.
- Separate observation from inference. "My Pro account shows a 5-hour reset" is a community report and will be labelled as one. "Pro resets every 5 hours" needs a source.
- Screenshots are evidence, not sources. They can support a Tier 4 note; they cannot promote a claim to fact.
What happens next
- The claim is checked against the highest-tier source available.
- The entity is updated, and its last verified date is bumped.
- If the change is material — a rename, an availability shift, a deprecation — it is added to that page's change log and appears in what's new and the RSS feed.
Where to send it
Submission handling is not wired up yet on this deployment. Until it is, the intended routes are a public issue tracker for corrections and a form for directory submissions — both linked from here once live. If you are running this site, replace this section with your actual contact route; leaving it vague is the fastest way to receive nothing.