Observation
The Available SDKs table in README.md has three columns: SDK, Location, and Installation.
The Location column currently links to cookbook READMEs in the external github/awesome-copilot repository (e.g.,cookbook/nodejs/, cookbook/python/, etc.), rather than to the actual SDK source subfolders within this repository (nodejs/, python/, go/, dotnet/).
This is confusing for a few reasons:
- Misleading column semantics — A column labeled "Location" in the SDK table naturally implies it points to where the SDK code lives (i.e., the subfolder in this repo), not to an external cookbook.
- Label vs. target mismatch — The link labels say
cookbook/nodejs/, cookbook/python/, etc., but they resolve to a completely different repository.
- The note below the table says "See the individual SDK READMEs for installation, usage examples, and API reference" — which reinforces the expectation that the links above point to those READMEs, not cookbooks.
Suggestion
Consider one of the following approaches:
- Option A: Change the Location column to point to the SDK subfolders in this repo (e.g.,
nodejs/, python/, etc.) and add a separate "Cookbook" column (or a note) linking to the external cookbook resources.
- Option B: Rename the "Location" column to "Cookbook" to make its purpose explicit, and add a separate "SDK Docs" column pointing to the subfolders in this repo.
- Option C: Keep three columns but re-label them for clarity: SDK, Docs (pointing to the subfolder READMEs), Cookbook (pointing to the external cookbook links), and Installation.
Observation
The Available SDKs table in
README.mdhas three columns: SDK, Location, and Installation.The Location column currently links to cookbook READMEs in the external
github/awesome-copilotrepository (e.g.,cookbook/nodejs/,cookbook/python/, etc.), rather than to the actual SDK source subfolders within this repository (nodejs/,python/,go/,dotnet/).This is confusing for a few reasons:
cookbook/nodejs/,cookbook/python/, etc., but they resolve to a completely different repository.Suggestion
Consider one of the following approaches:
nodejs/,python/, etc.) and add a separate "Cookbook" column (or a note) linking to the external cookbook resources.