What to report
- Wrong information about the owner, author, licence, price, compatibility, or installation.
- A broken link, archived repository, new release, or outdated summary.
- A category, task description, or scope statement that could mislead readers.
- A test report with the wrong component, version, setup, input, output, or calculation.
- A privacy, security, copyright, trademark, or impersonation concern.
How to ask for a correction
Email [email protected]. Include the page link, what you think is wrong, the correction you suggest, and a link to the original source that supports it. Tell us whether you are the creator, a contributor, a user, or someone else connected to the issue.
What happens next
- We read the request and decide how urgent it is.
- We compare the page with the official source, saved test evidence, and earlier versions of the page.
- We may ask you or the Skill creator for more information.
- We then correct the page, add a note, leave it unchanged, hide it while we investigate, or remove it.
A technical, ownership, or legal dispute may take longer to resolve than a broken link or simple factual error.
How we show a correction
We may fix a spelling or formatting error without adding a public note. A change to the meaning, credit, what was tested, or the result should include a new date or correction note.
If a report tested an older version, we keep that version in the record rather than making the result appear to cover a newer release.
Urgent issues
Put "URGENT" in the email subject if you find an exposed password or secret, active malware, a serious security risk, personal information that should not be public, or impersonation.
Do not include a working password, secret key, or sensitive personal information in the email.