Skill search box clears after each selection, forcing repeated typing for skills that share a keyword
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start at the skills picker in the new-profile flow and reproduce the behavior with the search term "cosmos". Trace the picker interaction and dropdown layout, then verify that selecting multiple matching skills preserves the query and keeps every result reachable within the viewport.
Written by the indexing model from the issue text.
Description
Original author: @JaGord
What happens
When I create a new profile and search for skills, the search box empties the moment I tick a skill's checkbox. If I want to add several skills that share a keyword, I have to type that keyword again for each one.
The Azure Cosmos DB agent kit has 13 matching skills, so I ended up typing "cosmos" and re-running the same search 13 times to select them all.
The results dropdown also runs past the bottom of the browser window and gets clipped, so the lower entries are hard to reach.
Steps to reproduce
- Start creating a new profile.
- Open the skills picker and type a keyword (for example, "cosmos").
- Tick one skill in the results.
- The search box resets to empty and the results collapse.
- Repeat for every remaining skill that matches the keyword.
Expected
- The search term stays in the box after I select a skill, so I can keep ticking matching results without retyping.
- The dropdown stays inside the viewport (or scrolls on its own) so every result is reachable.
Impact
Selecting all 13 Cosmos DB skills takes 13 separate searches instead of one. The problem grows with the number of skills that share a keyword.
Screenshot
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 5
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 17
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/scope
-
type: worker-update
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
type: worker-update
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
type: worker-update
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
author: JaGord documentation good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
author: cedricvidal bug portal
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
Similar issues
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
opensearch-project/security-dashboards-plugin#2545 ·
Maintainers usually reply within 1 day
-
Add: Dream TR SDOpencheck:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
doctor integrity sample scans soft-deleted pages on Postgres (batch path has no deleted_at filter)Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
SocialGouv/egapro#4672 · 1 comment ·
Maintainers usually reply within 2 days
-
area:agents area:tui bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anthropics/claude-code#98358 ·
Maintainers usually reply within 1 day