Copilot Studio skills show as "Unnamed" and stop triggering

(2) Share

Report

Posted on by Dmitrij Vagner

I like the new look of Copilot Studio because I'm not a very technical person, but I still want to create Copilot Studio agents 😉. The topics used to scare me, but I really appreciate skills because they make perfect sense to me.
However, when I tried to upload/create the first skill, the agent showed it as an 'unnamed' skill during use. Then, after I uploaded a second skill with a different name and instructions, the agent stopped using the first one and wouldn't trigger the second one either. Do you know what the issue might be and how to fix it?

My all skills have names (also descriptions and instructions):

Thanks in advance!

Categories:

Copilot Studio skills development

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Beyond The Platforms 246 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi Dmitrij,

The fact that the skill appears as "Unnamed" usually suggests that Copilot Studio isn't correctly reading the skill metadata during registration. Even if the name is visible in the authoring experience, I would double-check that the skill manifest is valid and that all required metadata (name, description, and actions) is being exposed correctly.

A few things I'd verify:

Remove the skill and register it again.

Confirm there were no validation or health-check errors during registration.

Make sure each skill has a very specific description and purpose, especially if multiple skills are available.

Temporarily keep only one skill enabled and test whether it gets triggered.

Microsoft documentation notes that skill registration issues or endpoint validation problems can prevent skills from being properly recognized and invoked by the orchestrator. If the metadata cannot be read correctly, unexpected behavior such as "Unnamed" skills or non-triggering skills may occur.

Could you share a screenshot of the skill configuration (or the skill manifest if applicable)? That would help identify whether this is a metadata issue, a registration issue, or an orchestration problem.

Hope this helps!
Paolo

✅ Did this solve your issue? → Accept as Solution
👍 Partially helpful? → Click "Yes" on "Was this reply helpful?" or drop a Like!

Want more tips on Power Platform & AI? Follow me here:

🔗 LinkedIn: https://www.linkedin.com/in/paoloasnaghi/
▶️ YouTube: https://www.youtube.com/@BeyondThePlatforms
📸 Instagram: https://www.instagram.com/beyond_the_platforms/
🌐 Website: https://www.beyondtheplatforms.com/

Was this reply helpful? Yes No
CU18110008-0 31 on at

Like
a
(2)

Report
Copy link

Link copied!

I'm running into the exact same issue.
Taking it a step further, but I asked my agent to identify what skills I have and it cant recognize any of my skills anymore and it only shows the default analyzing skills (I have 7 additional skills I made that arent being detected). They were recognized about 2 days ago though so this is out of nowhere.

Was this reply helpful? Yes No
Dmitrij Vagner 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CU18110008-0, try to download and use (just write "log the call") this skill: dataverse-business-skills/skills/log-call-transcripts/SKILL.md at main · microsoft/dataverse-business-skills in your agent and let me know if it works. Thanks.

Was this reply helpful? Yes No