[UX] Improve the experience of the "Abilities" page
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start at the Abilities page implementation and trace the Execute action, parameter display, and transition to the Chat view. Define the behavior for abilities with and without inputs, then verify that missing inputs are prompted for and execution results are visible in Chat.
Written by the indexing model from the issue text.
Description
This is more of a question / discussion point about some of the abilities in the Abilities page:
Is the purpose of this page to showcase the abilities or to actually execute a specific task? For example, in this page there is the Activate plugin ability. This ability expects an input, like the plugin name, however:
- User is not prompted to specify a parameter unless they specifically specify it upfront by clicking the Show paramters link
- When you click Execute there is "no visual response" to the user" because the output is shown at the top, which is not always visible to the user, depending on the screen size.
- In this case, the execution fails:
We can improve this by doing the following:
- If the user executes an ability that does not require any further inputs, like List users, the user should be redirected to the Chat view to see the output.
- If the user executes an ability that requires input and they did not specify an input, the user should be prompted to specify the input, and then the ability should execute in the chat window.
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 6
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
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 pluginslab/wp-agentic-admin
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pluginslab/wp-agentic-admin#226 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
pluginslab/wp-agentic-admin#215 ·
-
WP.org submission: close out review T4 (17 Jun) and stop the review loopMay be free again @ivdimova claimed this 39 days ago, and no pull request is open. Openphp question wporg-submission
pluginslab/wp-agentic-admin#228 · 5 comments · 2 assignees ·
-
enhancement react-js ux
Difficulty 5/5 Over a week Newbie friendliness 35/100
pluginslab/wp-agentic-admin#224 ·
-
enhancement ux
Difficulty 4/5 3-5 days Newbie friendliness 48/100
pluginslab/wp-agentic-admin#223 ·
All issues in pluginslab/wp-agentic-admin
Similar issues
-
Complexity: Small P-Feature: Projects page ready for merge team role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
bellingcat/toolkit#905 ·
-
self-care self-care:docs-build-time-investigator
Difficulty 2/5 Half a day Newbie friendliness 76/100
githubnext/gh-aw-cao#14191 ·
Maintainers usually reply within 1 day
-
effort:low impact:medium RAG status: auto-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mastra-ai/mastra#25229 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sugarlabs/musicblocks#8984 ·
Maintainers usually reply within 1 day