Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- At 12:33 UTC on October 13, Cursor staff member Colin clarified that synced personal skills are unavailable in automations with or without a repository, including runs set to Run as you.
- For a repository-based task, put the skill at .cursor/skills/your-skill-name/SKILL.md in the repository the automation uses, and select that same repository. The staff example uses sentry-jira-triage.
- For a task without a repository, paste the actual skill instructions into the automation instructions. Typing /skill-name or asking the agent to use a named skill does not supply the missing synced content.
- The issue now covers both runtime access and the slash menu. No fix version or delivery date was announced; a repository copy is a temporary way to provide content, not restored personal-skill synchronization.
The correction covers runtime access, not just the menu
On October 13, 2026, a user reported on Cursor’s official forum that a personal skill created on the desktop and synced to the cloud appeared in a Cloud Agent’s slash menu but was unavailable in an automation. The reported environment was macOS and the Cursor website that day. This article did not reproduce the case or test every operating system and client.
Colin’s initial reply at 11:59 UTC said personal skills would still load when Run as you was selected. After the user reported otherwise, he corrected that answer at 12:33 UTC: synced personal skills are currently unavailable in automation runs with or without a repository, even with Run as you.
A skill is a reusable set of instructions for an agent. Seeing its name in a menu and having its instructions available at runtime are separate checks. Follow the later, complete correction; manually typing the name is no longer the recommended way to address this missing content.
With a repository, put the instructions in the selected repo
First, provide SKILL.md in the repository the automation actually uses. The staff example is .cursor/skills/sentry-jira-triage/SKILL.md. Supply the skill’s actual instructions there, rather than just its name or a reference to your personally synced content.
Next, select that same repository in the automation. The staff reply says skills in this folder are picked up automatically. Repository files and account-synced personal skills are different sources of instructions; selecting a repository does not restore personal synchronization.
Then check that the selected repository contains the intended rules. This is editorial advice: match the file path and content to the task. A menu entry, or the agent saying it used a skill, is not enough on its own to confirm the setup.
Without a repository, paste the full instructions
If the task should not be associated with a repository, the other staff-recommended workaround is to paste the skill’s instructions directly into the automation instructions. Keep the task’s goal, then provide the steps, output requirements and limits needed to carry it out.
Typing /sentry-jira-triage, or simply asking the agent to use the sentry-jira-triage skill, still only names the skill. The corrected reply explicitly says that typing a name will not make the synced personal skill available. Supply the content itself.
This makes the rules part of that task’s own instructions. When your personal skill changes, check whether the text retained in the task still matches your requirements. That is maintenance advice, not an announcement that synchronization has been fixed.
Check that the rules are available, not just the name
Hypothetical, unexecuted example: a scheduled task should summarize errors before preparing proposed tickets. If the rules are in a repository, select that repository and provide the file above. If the task should have no repository, paste the same rules directly. This example explains the choice; no Sentry or Jira connection or automation run was performed for this article.
As an editorial check, begin with a task that will not create tickets or change an external system. Ask the agent to outline the steps and expected output from the supplied rules, then compare the outline with their important limits. This is suggested verification, not an independently tested result or a platform guarantee.
For real work, check separately whether the rules are readable, required tools already have authorization, and the actual output meets your requirements. Finding a repository skill does not prove that external tools are connected, the task succeeded, or the slash menu has been fixed.
An earlier repository success does not prove sync works
Colin suggested that earlier apparent success with a repository most likely came from a copy of the skill in that repository’s files. That is a staff explanation, not a finding proven by individual run logs. It does not establish that personal skills sometimes sync into automations.
He expanded the report to cover both the automation run and the slash menu and passed it to the team. The reply names no fix version, delivery date, plan eligibility, fee or country list. Follow explicit updates in the original thread and check their scope; an ordinary upgrade alone is not evidence that access has been restored.
Sources
Frequently Asked Questions
Why does a skill visible in a regular Cloud Agent not prove an automation can use it?
The original user reported exactly that difference between the two entry points. The corrected staff reply confirms that synced personal content is currently unavailable inside automation runs. A name shown in a regular Cloud Agent’s menu does not establish the automation’s source of instructions.
Must the repository directory be named sentry-jira-triage?
That name is the staff example. For your own skill name, retain the .cursor/skills/your-skill-name/SKILL.md structure, supply the actual rules, and select the repository containing the file. This article did not separately verify every naming or file-format requirement.
Does the repository workaround also fix slash-menu autocomplete?
The corrected reply says skills in the repository folder are picked up, but it does not announce a menu fix. Check instruction availability and the editor’s displayed names separately; the workaround is not an identified UI fix release.
Should I copy passwords or private keys into the skill instructions?
Providing rules does not require expanding credential access. As editorial advice, keep existing authorized connections and separate operating instructions from secrets. Do not paste passwords, private keys or private links into the repository file or task instructions. The forum reply does not ask you to do so.