feat: update readme and skills (#1418)

* feat: update readme and skills

* Update plugins/context-matic/README.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Alishahzad1903
2026-04-17 05:57:35 +05:00
committed by GitHub
parent 5aa80658b0
commit ddfc3e205a
3 changed files with 20 additions and 18 deletions

View File

@@ -51,8 +51,10 @@ Check whether guidelines and skills have already been added for this project by
Call **fetch_api** to find available APIs — always start here.
- Provide the `language` parameter using the language detected in step 1a.
- The response returns available APIs with their names, descriptions, and `key` values.
- Always provide the `language` parameter using the language detected in step 1a.
- Always provide the `key` parameter: pass the API name/key from the user's request (e.g. `"paypal"`, `"twilio"`).
- If the user did not provide an API name/key, ask them which API they want to integrate, then call `fetch_api` with that value.
- The tool returns only the matching API on an exact match, or the full API catalog (name, description, and `key`) when there is no exact match.
- Identify the API that matches the user's request based on the name and description.
- Extract the correct `key` for the user's requested API before proceeding. This key will be used for all subsequent tool calls related to that API.
@@ -94,7 +96,7 @@ Call **update_activity** (with the appropriate `milestone`) whenever one of thes
- [ ] Project's primary language detected (step 1a)
- [ ] `add_guidelines` called if guideline files were missing, otherwise skipped
- [ ] `add_skills` called if `{language}-conventions` was missing, otherwise skipped
- [ ] `fetch_api` called with correct `language` for the project
- [ ] `fetch_api` called with correct `language` and `key` (API name)
- [ ] Correct `key` identified for the requested API (or user informed if not found)
- [ ] `update_activity` called only when a milestone is concretely reached in code/infrastructure — never for questions, searches, or tool lookups
- [ ] `update_activity` called with the appropriate `milestone` at each integration milestone