Contact support
Email [email protected] for help with FeedSkills downloads, installation or a Skill that does not work as described.
We provide a first human reply within three business days. This is a response time, not a promise to resolve every issue in three days.
Account access and email recovery
If you can no longer use the email on your FeedSkills account, contact support for a manual account recovery review. Tell us the email previously used for the account (or your account ID if you can still see it), and the new email you control. We verify the original account and your control of the new address before making a change.
A payment screenshot or checkout email by itself is not enough to verify account ownership. We do not offer a public self-service merge. If the new email already belongs to another FeedSkills account, we will not merge or transfer either account. If the evidence is insufficient, we leave the account and its access unchanged and explain the next step.
An approved recovery keeps the existing account, downloads and orders attached to that account. Existing browser and CLI access, linked Google sign-in, pending authorizations, email codes, sign-in links and device approvals stop working after the change. Marketing consent is reset, so the new email must opt in again. The old email may later create a separate account, without the recovered account's access.
Never send passwords, API keys, sign-in codes, sign-in links, device codes or identity documents by email. We will ask for only the minimum information needed for the review.
Account deletion
Contact support to request account deletion. This is a manual review; there is no self-service deletion control. Before processing the request, we verify account ownership and ask you to confirm that you backed up anything you want to keep and understand that deletion stops FeedSkills sign-in, online re-downloads and updates. FeedSkills does not delete files from your computer.
Deletion does not automatically issue a refund or cancel the right to use versions already downloaded under an order that has not been refunded. It ends the account's online access. We remove the active login email, marketing consent and unnecessary authentication artifacts, while retaining a minimal redacted deletion case and the minimum order, entitlement, payment, refund and audit facts needed to establish what happened.
Creem's external merchant-of-record records are not deleted by this local request. Its Merchant Terms describe at least seven years of records related to sold products as a platform contract requirement, not a statement of a local statutory deadline. Other local records follow a purpose-based internal retention schedule. Temporary credentials and checkout data have shorter review periods than necessary transaction and audit facts; restricted backup history and Creem records are handled separately. Expiry does not mean every record has already been erased. Test checkout and account-delivery fixtures are isolated from real purchases and do not grant production access.
Help us reproduce the issue
- The Skill name and version, and the page or download link you used.
- Your operating system, Agent and the steps that led to the problem.
- What you expected and what happened, with a short error message if available.
Remove passwords, API keys, login links and private client material before sending screenshots or logs. We will ask if we need a small, non-sensitive example.
How we handle requests
Delivery failures and duplicate charges receive priority. Routine defects are handled in our weekly maintenance work; we will explain the next step when we reply. Support does not include one-to-one coaching or done-for-you video production.
Founding Membership includes the Members Skills. See Pricing for the current availability of free and paid Skills.
Before you write
Check the Skill's stated inputs, dependencies and tested environments. Our getting-started guide explains the current installation path, and the privacy policy describes how this website handles data.