Contact
Get in touch
One address, for everything. SkillAppMD has no support portal and no ticket queue, so mail reaches a person.
Pick the closest reason below and the subject line will be filled in for you. It is not required, it just gets the request to the right place faster.
Correction or removal
You are named in the index, or a repository you own appears, and you want it corrected or taken down. This route exists because the people in the index did not opt in, and requests are acted on rather than triaged away.
Attribution or licence problem
A record shows the wrong repository or owner, or the licence position is wrong. Rights are the point of this index, so a wrong one is a defect, not a detail.
Something else
Questions about how resolution works, the API, or using SkillAppMD with your agent.
What to include in a removal request
A request with these four things can be acted on immediately. Without them we have to write back and ask, which only slows it down for you.
- 01The repositoryAs owner/repo, or a link to it.
- 02What is wrongRemoval, or a correction. If a correction, what the right value is.
- 03Your relationship to itOwner, author, or acting for the owner. We do not need documents, just a plain statement.
- 04A reply addressSo we can confirm the outcome. It is used for that and nothing else.
Every request is recorded with its outcome and the time it was handled. What we store is set out in the privacy page.
What we cannot help with
SkillAppMD indexes public repositories and does not host the files themselves. If a skill’s content is wrong, unsafe or broken, that belongs with the repository that published it, not with us. We can correct what the index says about it, and we can remove it from the index.