gravity-cli 0.4.4__tar.gz → 0.5.2__tar.gz

{gravity_cli-0.4.4 → gravity_cli-0.5.2}/AGENT_STANDARD.md

@@ -191,6 +191,17 @@ model = ChatOpenAI(model="openai/gpt-6-luna",
                    api_key=os.environ["GRAVITY_RUN_TOKEN"])
 ```
 
+**Embeddings** use the same URL and token (`<GRAVITY_LLM_URL>/embeddings`), metered
+and budgeted like chat calls:
+
+```python
+emb = OpenAIEmbeddings(model="voyageai/voyage-4-lite",   # or google/gemini-embedding-2
+                       base_url=os.environ["GRAVITY_LLM_URL"],
+                       api_key=os.environ["GRAVITY_RUN_TOKEN"],
+                       check_embedding_ctx_length=False)  # send text, not OpenAI token ids
+vectors = await emb.aembed_documents(["first text", "second text"])
+```
+
 Those three env vars — `GRAVITY_GATEWAY_URL`, `GRAVITY_LLM_URL`,
 `GRAVITY_RUN_TOKEN` — are the entire Gravity surface, plus the `gravity`
 package for tools on the platform (§8). No `OPENAI_API_KEY`: locally and in
@@ -271,7 +282,10 @@ start**: everything before the call happens twice.
 replaced. State is kept per thread. A key the next run doesn't send keeps its
 value (a monitor's `seen`, a draft). For memory shared by one consumer's
 threads, use `langgraph.config.get_store()` (`aget` / `aput` / `asearch` by
-namespace and filter; no semantic search).
+namespace and filter; no semantic search). It is kept per consumer and agent,
+across runs and versions, until the agent deletes an item (`aput(ns, key, None)`);
+store one item per record, not one large blob. `gravity run` gives you the same
+store locally, saved in `.gravity/store.json` (delete it to start over).
 
 **Conversation.** `messages` must use the `add_messages` reducer:
 `messages: Annotated[list, add_messages]`. Each turn the platform sends only

gravity_cli-0.4.4/README.md → gravity_cli-0.5.2/PKG-INFO

@@ -1,3 +1,20 @@
+Metadata-Version: 2.5
+Name: gravity-cli
+Version: 0.5.2
+Summary: gravity cli — init, run, and push python agents to the Gravity marketplace
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.12
+Requires-Dist: gravity-schema==0.5.2
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: keyring>=25.0.0
+Requires-Dist: python-dotenv>=1.0.0
+Requires-Dist: rich>=13.9.0
+Requires-Dist: typer>=0.15.0
+Requires-Dist: uv>=0.8.0
+Description-Content-Type: text/markdown
+
 <h1 align="center">Gravity CLI</h1>
 
 <p align="center">
@@ -161,8 +178,8 @@ gravity push
 
 | Service | What it does | Used by |
 |---|---|---|
-| **Gateway** | Serves tools over MCP (`/mcp`) and models over an OpenAI-compatible API (`/v1`). Issues run tokens and refuses any tool a run was not granted. | `run`, `schedule`, `adapt`, and your agent |
-| **Control plane** | Accounts, the tool catalog, pushed agents, builds and hosted runs. | `login`, `logout`, `whoami`, `push`, `tools`, `agents`, `runs`, `logs` |
+| **Gateway** | Serves tools over MCP (`/mcp`) and models over an OpenAI-compatible API (`/v1`). Lists its tools at `/tools` and your connected accounts at `/connections`. Issues run tokens and refuses any tool a run was not granted. | `run`, `schedule`, `adapt`, `tools`, `connect`, and your agent |
+| **Control plane** | Accounts, pushed agents, builds and hosted runs. | `login`, `logout`, `whoami`, `push`, `agents`, `runs`, `logs` |
 
 On `gravity run`, the CLI trades your dev token for a run token scoped to the manifest's tools and starts the agent with only that token. Your own tokens are removed from the agent's environment, so agent code can never act as you.
 
@@ -190,6 +207,7 @@ Run `gravity help` for this list in the terminal, and add `-h` to any command fo
 | **Account** | [`gravity login`](#gravity-login) | Sign in to Gravity in your browser |
 | | [`gravity logout`](#gravity-logout) | Sign out |
 | | [`gravity whoami`](#gravity-whoami) | Show who you are signed in as |
+| | [`gravity connect`](#gravity-connect) | Connect an account your agents act on (Gmail, Slack...) |
 | **Help** | [`gravity guide`](#gravity-guide) | Read the builder guide: how to build a good agent |
 | | [`gravity help`](#gravity-help) | Show the list of commands |
 
@@ -238,7 +256,10 @@ What it checks:
 - the entrypoint file exists and defines the object the manifest names
 - `requirements.txt` exists, and compiles into `requirements.lock` for the platform image (ARM64 Linux) and the manifest's Python version
 - every adapter a slot declares has a file, and every adapter file is declared
-- warnings, never failures, for tool names or network libraries in your code that the manifest does not declare
+- every tool in the manifest exists in the catalog, the same list the platform's build uses, so a typo fails here instead of after a push
+- every imported write tool is under `approvals.required_for`
+- your code never names a write tool the manifest does not grant
+- a warning, never a failure, for read tools your code names but the manifest does not declare
 
 ```bash
 gravity validate
@@ -376,7 +397,9 @@ gravity logs <run_id>
 
 ### `gravity tools`
 
-Browse the tool catalog: the names you can put under `permissions.tools`, with a description and the access each one needs.
+Browse the tool catalog: the names you can put under `permissions.tools`, with what each one does. It is the gateway's own list, so it shows exactly what a run can call, and it needs no sign-in.
+
+About 25 tools are curated, such as `gmail.read` and `web.search`. The other ~1,100 are imported from the same apps and unreviewed: any imported tool that changes something must also be under `approvals.required_for`, and `gravity validate` checks that.
 
 ```
 gravity tools [search]
@@ -412,6 +435,23 @@ gravity whoami
 gravity whoami --token    # print the gateway token itself, for CI or a teammate's .env
 ```
 
+### `gravity connect`
+
+Connect an account your agents' tools act on, through the app's own sign-in page in your browser. With no app, list what is connected.
+
+```
+gravity connect [app]
+```
+
+```bash
+gravity connect           # what is connected, and whose accounts runs act on
+gravity connect gmail     # opens the sign-in page, then waits until it is done
+gravity connect sheets    # use the app name from tool names: sheets, calendar, drive, linear, slack, github...
+```
+
+- Uses the gateway token from `gravity login`.
+- `web` tools need no account.
+
 ### `gravity guide`
 
 Read the builder guide, which ships with the CLI: how an agent is put together, the rules your code must follow, formatting results, approvals, adapters, scheduling, memory, and a checklist.
@@ -472,7 +512,8 @@ Never commit a `.env` file. The `.gitignore` in every template keeps `.env` and
 |---|---|---|---|
 | Create, check and package an agent | `init`, `validate`, `build` | nothing | nothing |
 | Run an agent locally | `run`, `schedule`, `adapt` | `gravity login` (or `GRAVITY_DEV_TOKEN`) | nothing |
-| Publish and inspect agents | `push`, `tools`, `agents`, `runs`, `logs`, `whoami` | `gravity login` | nothing |
+| Publish and inspect agents | `push`, `agents`, `runs`, `logs`, `whoami` | `gravity login` | nothing |
+| Browse tools, connect accounts | `tools`, `connect` | nothing for `tools`; `gravity login` for `connect` | nothing |
 
 Set `GRAVITY_API_URL` and `GRAVITY_GATEWAY_URL` only to work against services you run yourself; see [Running a local gateway](#running-a-local-gateway).
 
@@ -714,6 +755,8 @@ Real tools act on a connected account. Connect one with `gravity-gateway connect
 
 ## What's new
 
+- **0.5.2** Jira, Confluence and Notion join the catalog: 1,351 tools across 11 apps. `get_store()` works in local runs, kept in `.gravity/store.json`. Renewing an expired sign-in keeps your gateway token, so `gravity run` keeps working after an hour. Commands start faster: the catalog loads in a quarter of the time.
+- **0.5.0** `gravity connect` links your own accounts. `web.search` and `web.fetch` join the catalog. `gravity validate` now refuses a tool that isn't in the catalog, an imported write tool without an approval, and code that names a write tool the manifest doesn't grant. `gravity tools` reads the gateway's list and needs no sign-in. On Windows the session stays in the keychain instead of a file.
 - **0.4.4** Same code as 0.4.3, released from this repository so the GitHub release, the tag and PyPI line up again. Adds `RELEASING.md`.
 - **0.4.3** Documents the `secret` input type and the `supadata.get_transcript` tool.
 - **0.4.1** New input type `secret` for an API key, password or other confidential value. New built-in tool `supadata.get_transcript` (`gravity tools supadata`).

gravity_cli-0.4.4/PKG-INFO → gravity_cli-0.5.2/README.md

@@ -1,20 +1,3 @@
-Metadata-Version: 2.5
-Name: gravity-cli
-Version: 0.4.4
-Summary: gravity cli — init, run, and push python agents to the Gravity marketplace
-License-Expression: Apache-2.0
-License-File: LICENSE
-License-File: NOTICE
-Requires-Python: >=3.12
-Requires-Dist: gravity-schema==0.4.4
-Requires-Dist: httpx>=0.27.0
-Requires-Dist: keyring>=25.0.0
-Requires-Dist: python-dotenv>=1.0.0
-Requires-Dist: rich>=13.9.0
-Requires-Dist: typer>=0.15.0
-Requires-Dist: uv>=0.8.0
-Description-Content-Type: text/markdown
-
 <h1 align="center">Gravity CLI</h1>
 
 <p align="center">
@@ -178,8 +161,8 @@ gravity push
 
 | Service | What it does | Used by |
 |---|---|---|
-| **Gateway** | Serves tools over MCP (`/mcp`) and models over an OpenAI-compatible API (`/v1`). Issues run tokens and refuses any tool a run was not granted. | `run`, `schedule`, `adapt`, and your agent |
-| **Control plane** | Accounts, the tool catalog, pushed agents, builds and hosted runs. | `login`, `logout`, `whoami`, `push`, `tools`, `agents`, `runs`, `logs` |
+| **Gateway** | Serves tools over MCP (`/mcp`) and models over an OpenAI-compatible API (`/v1`). Lists its tools at `/tools` and your connected accounts at `/connections`. Issues run tokens and refuses any tool a run was not granted. | `run`, `schedule`, `adapt`, `tools`, `connect`, and your agent |
+| **Control plane** | Accounts, pushed agents, builds and hosted runs. | `login`, `logout`, `whoami`, `push`, `agents`, `runs`, `logs` |
 
 On `gravity run`, the CLI trades your dev token for a run token scoped to the manifest's tools and starts the agent with only that token. Your own tokens are removed from the agent's environment, so agent code can never act as you.
 
@@ -207,6 +190,7 @@ Run `gravity help` for this list in the terminal, and add `-h` to any command fo
 | **Account** | [`gravity login`](#gravity-login) | Sign in to Gravity in your browser |
 | | [`gravity logout`](#gravity-logout) | Sign out |
 | | [`gravity whoami`](#gravity-whoami) | Show who you are signed in as |
+| | [`gravity connect`](#gravity-connect) | Connect an account your agents act on (Gmail, Slack...) |
 | **Help** | [`gravity guide`](#gravity-guide) | Read the builder guide: how to build a good agent |
 | | [`gravity help`](#gravity-help) | Show the list of commands |
 
@@ -255,7 +239,10 @@ What it checks:
 - the entrypoint file exists and defines the object the manifest names
 - `requirements.txt` exists, and compiles into `requirements.lock` for the platform image (ARM64 Linux) and the manifest's Python version
 - every adapter a slot declares has a file, and every adapter file is declared
-- warnings, never failures, for tool names or network libraries in your code that the manifest does not declare
+- every tool in the manifest exists in the catalog, the same list the platform's build uses, so a typo fails here instead of after a push
+- every imported write tool is under `approvals.required_for`
+- your code never names a write tool the manifest does not grant
+- a warning, never a failure, for read tools your code names but the manifest does not declare
 
 ```bash
 gravity validate
@@ -393,7 +380,9 @@ gravity logs <run_id>
 
 ### `gravity tools`
 
-Browse the tool catalog: the names you can put under `permissions.tools`, with a description and the access each one needs.
+Browse the tool catalog: the names you can put under `permissions.tools`, with what each one does. It is the gateway's own list, so it shows exactly what a run can call, and it needs no sign-in.
+
+About 25 tools are curated, such as `gmail.read` and `web.search`. The other ~1,100 are imported from the same apps and unreviewed: any imported tool that changes something must also be under `approvals.required_for`, and `gravity validate` checks that.
 
 ```
 gravity tools [search]
@@ -429,6 +418,23 @@ gravity whoami
 gravity whoami --token    # print the gateway token itself, for CI or a teammate's .env
 ```
 
+### `gravity connect`
+
+Connect an account your agents' tools act on, through the app's own sign-in page in your browser. With no app, list what is connected.
+
+```
+gravity connect [app]
+```
+
+```bash
+gravity connect           # what is connected, and whose accounts runs act on
+gravity connect gmail     # opens the sign-in page, then waits until it is done
+gravity connect sheets    # use the app name from tool names: sheets, calendar, drive, linear, slack, github...
+```
+
+- Uses the gateway token from `gravity login`.
+- `web` tools need no account.
+
 ### `gravity guide`
 
 Read the builder guide, which ships with the CLI: how an agent is put together, the rules your code must follow, formatting results, approvals, adapters, scheduling, memory, and a checklist.
@@ -489,7 +495,8 @@ Never commit a `.env` file. The `.gitignore` in every template keeps `.env` and
 |---|---|---|---|
 | Create, check and package an agent | `init`, `validate`, `build` | nothing | nothing |
 | Run an agent locally | `run`, `schedule`, `adapt` | `gravity login` (or `GRAVITY_DEV_TOKEN`) | nothing |
-| Publish and inspect agents | `push`, `tools`, `agents`, `runs`, `logs`, `whoami` | `gravity login` | nothing |
+| Publish and inspect agents | `push`, `agents`, `runs`, `logs`, `whoami` | `gravity login` | nothing |
+| Browse tools, connect accounts | `tools`, `connect` | nothing for `tools`; `gravity login` for `connect` | nothing |
 
 Set `GRAVITY_API_URL` and `GRAVITY_GATEWAY_URL` only to work against services you run yourself; see [Running a local gateway](#running-a-local-gateway).
 
@@ -731,6 +738,8 @@ Real tools act on a connected account. Connect one with `gravity-gateway connect
 
 ## What's new
 
+- **0.5.2** Jira, Confluence and Notion join the catalog: 1,351 tools across 11 apps. `get_store()` works in local runs, kept in `.gravity/store.json`. Renewing an expired sign-in keeps your gateway token, so `gravity run` keeps working after an hour. Commands start faster: the catalog loads in a quarter of the time.
+- **0.5.0** `gravity connect` links your own accounts. `web.search` and `web.fetch` join the catalog. `gravity validate` now refuses a tool that isn't in the catalog, an imported write tool without an approval, and code that names a write tool the manifest doesn't grant. `gravity tools` reads the gateway's list and needs no sign-in. On Windows the session stays in the keychain instead of a file.
 - **0.4.4** Same code as 0.4.3, released from this repository so the GitHub release, the tag and PyPI line up again. Adds `RELEASING.md`.
 - **0.4.3** Documents the `secret` input type and the `supadata.get_transcript` tool.
 - **0.4.1** New input type `secret` for an API key, password or other confidential value. New built-in tool `supadata.get_transcript` (`gravity tools supadata`).

{gravity_cli-0.4.4 → gravity_cli-0.5.2}/packages/gravity-schema/gravity_schema/__init__.py

@@ -36,7 +36,9 @@ from .manifest import (
     StateSpec,
     TriggersSpec,
 )
+from .source_scan import is_agent_source, undeclared_write_tools
 from .validation import (
+    check_imported_write_approvals,
     check_tool_references,
     load_manifest_file,
     load_manifest_text,
@@ -73,6 +75,10 @@ __all__ = [  # noqa: RUF022 - grouped by concern, not alphabetical
     "load_manifest_text",
     "load_manifest_file",
     "check_tool_references",
+    "check_imported_write_approvals",
+    # source scan
+    "is_agent_source",
+    "undeclared_write_tools",
     # catalog
     "ToolCatalog",
     "StaticToolCatalog",

{gravity_cli-0.4.4 → gravity_cli-0.5.2}/packages/gravity-schema/gravity_schema/catalog.py

@@ -10,6 +10,13 @@ from typing import Protocol
 
 import yaml
 
+# libyaml's parser, about 8x faster: every CLI command loads the whole catalog at import.
+_LOADER = getattr(yaml, "CSafeLoader", yaml.SafeLoader)
+
+
+def _load(text: str):
+    return yaml.load(text, Loader=_LOADER)
+
 
 class ToolCatalog(Protocol):
     def exists(self, tool_name: str) -> bool: ...
@@ -39,6 +46,7 @@ class ToolEntry:
     breadth: str  # generic | niche
     guarantee: str  # certified | community | experimental
     side_effect: str  # read | write
+    toolkit: str | None = None  # the account a user connects for it; None when none is needed
 
 
 _BREADTH = {"generic", "niche"}
@@ -48,12 +56,12 @@ _SIDE_EFFECT = {"read", "write"}
 
 def load_catalog(path: Path | None = None) -> tuple[ToolEntry, ...]:
     """Parse and check catalog.yaml; a malformed entry fails at import."""
-    raw = yaml.safe_load((path or Path(__file__).with_name("catalog.yaml")).read_text(encoding="utf-8"))
+    raw = _load((path or Path(__file__).with_name("catalog.yaml")).read_text(encoding="utf-8"))
     # catalog_imported.yaml (`gravity-gateway sync-tools`): the same apps' other tools,
     # experimental. Absent until the first sync; never read for an explicit path.
     imported = Path(__file__).with_name("catalog_imported.yaml")
     if path is None and imported.is_file():
-        raw = [*raw, *(yaml.safe_load(imported.read_text(encoding="utf-8")) or [])]
+        raw = [*raw, *(_load(imported.read_text(encoding="utf-8")) or [])]
     entries: list[ToolEntry] = []
     for item in raw:
         entry = ToolEntry(
@@ -64,6 +72,7 @@ def load_catalog(path: Path | None = None) -> tuple[ToolEntry, ...]:
             breadth=item["breadth"],
             guarantee=item["guarantee"],
             side_effect=item["side_effect"],
+            toolkit=item.get("toolkit"),
         )
         problems = []
         if entry.breadth not in _BREADTH:

{gravity_cli-0.4.4 → gravity_cli-0.5.2}/packages/gravity-schema/gravity_schema/catalog.yaml

@@ -10,6 +10,7 @@
 # Fields
 #   name         the Gravity name builders write in permissions.tools
 #   slug         the vendor action it routes to; null for a gateway built-in
+#   toolkit      the account a user connects for it (gravity connect); null when none is needed
 #   description  what a builder or a model reads to choose it
 #   scopes       the consent a consumer grants when connecting
 #   breadth      generic: ordinary plumbing any agent might use
@@ -21,14 +22,34 @@
 
 - name: example.echo
   slug: null
+  toolkit: null
   description: echoes back its input, for templates and plumbing tests
   scopes: []
   breadth: generic
   guarantee: certified
   side_effect: read
 
+- name: web.search
+  slug: COMPOSIO_SEARCH_WEB
+  toolkit: composio_search
+  description: search the web; returns results with titles, links and snippets. No account needed
+  scopes: []
+  breadth: generic
+  guarantee: certified
+  side_effect: read
+
+- name: web.fetch
+  slug: COMPOSIO_SEARCH_FETCH_URL_CONTENT
+  toolkit: composio_search
+  description: read the text content of a web page by its URL. No account needed
+  scopes: []
+  breadth: generic
+  guarantee: certified
+  side_effect: read
+
 - name: supadata.get_transcript
   slug: null
+  toolkit: null
   description: fetch the transcript of a YouTube video with the caller's own Supadata API key (api_key argument)
   scopes: []
   breadth: niche
@@ -37,6 +58,7 @@
 
 - name: gmail.read
   slug: GMAIL_FETCH_EMAILS
+  toolkit: gmail
   description: read the connected Gmail inbox
   scopes: [gmail.readonly]
   breadth: generic
@@ -45,6 +67,7 @@
 
 - name: gmail.draft
   slug: GMAIL_CREATE_EMAIL_DRAFT
+  toolkit: gmail
   description: create a Gmail draft
   scopes: [gmail.compose]
   breadth: generic
@@ -53,6 +76,7 @@
 
 - name: gmail.send
   slug: GMAIL_SEND_EMAIL
+  toolkit: gmail
   description: send an email from the connected Gmail
   scopes: [gmail.send]
   breadth: generic
@@ -61,6 +85,7 @@
 
 - name: sheets.read
   slug: GOOGLESHEETS_BATCH_GET
+  toolkit: googlesheets
   description: read values from a connected Google Sheet
   scopes: [sheets]
   breadth: generic
@@ -69,6 +94,7 @@
 
 - name: sheets.append
   slug: GOOGLESHEETS_BATCH_UPDATE
+  toolkit: googlesheets
   description: append a row to a connected Google Sheet
   scopes: [sheets]
   breadth: generic
@@ -77,6 +103,7 @@
 
 - name: slack.send
   slug: SLACK_SEND_MESSAGE
+  toolkit: slack
   description: post a message to a connected Slack channel
   scopes: [slack.chat:write]
   breadth: generic
@@ -85,6 +112,7 @@
 
 - name: slack.list_channels
   slug: SLACK_LIST_ALL_CHANNELS
+  toolkit: slack
   description: list channels in the connected Slack workspace
   scopes: [slack.channels:read]
   breadth: generic
@@ -93,6 +121,7 @@
 
 - name: slack.read_history
   slug: SLACK_FETCH_CONVERSATION_HISTORY
+  toolkit: slack
   description: read message history of a Slack channel
   scopes: [slack.channels:history]
   breadth: generic
@@ -101,6 +130,7 @@
 
 - name: slack.find_user
   slug: SLACK_FIND_USERS
+  toolkit: slack
   description: find a Slack user by name, handle or email, for mentions
   scopes: [slack.users:read]
   breadth: generic
@@ -109,6 +139,7 @@
 
 - name: calendar.read
   slug: GOOGLECALENDAR_EVENTS_LIST
+  toolkit: googlecalendar
   description: list events on the connected Google Calendar
   scopes: [calendar.readonly]
   breadth: generic
@@ -117,6 +148,7 @@
 
 - name: drive.read
   slug: GOOGLEDRIVE_DOWNLOAD_FILE
+  toolkit: googledrive
   description: download a file from the connected Google Drive
   scopes: [drive.readonly]
   breadth: generic
@@ -125,6 +157,7 @@
 
 - name: linear.create_issue
   slug: LINEAR_CREATE_LINEAR_ISSUE
+  toolkit: linear
   description: create an issue in a connected Linear team
   scopes: [linear.write]
   breadth: generic
@@ -133,6 +166,7 @@
 
 - name: linear.list_teams
   slug: LINEAR_LIST_LINEAR_TEAMS
+  toolkit: linear
   description: list the connected Linear workspace teams
   scopes: [linear.read]
   breadth: generic
@@ -141,6 +175,7 @@
 
 - name: linear.list_issues
   slug: LINEAR_LIST_LINEAR_ISSUES
+  toolkit: linear
   description: list open issues in the connected Linear workspace
   scopes: [linear.read]
   breadth: generic
@@ -149,6 +184,7 @@
 
 - name: linear.get_issue
   slug: LINEAR_GET_LINEAR_ISSUE
+  toolkit: linear
   description: read one Linear issue by id
   scopes: [linear.read]
   breadth: generic
@@ -158,6 +194,7 @@
 # GitHub: read-only, for change summaries and contribution profiles.
 - name: github.list_commits
   slug: GITHUB_LIST_COMMITS
+  toolkit: github
   description: list commits on a repository branch, filterable by date range, author or path
   scopes: [repo]
   breadth: generic
@@ -166,6 +203,7 @@
 
 - name: github.get_commit
   slug: GITHUB_GET_A_COMMIT
+  toolkit: github
   description: read one commit with its changed files, line counts and patches
   scopes: [repo]
   breadth: generic
@@ -174,6 +212,7 @@
 
 - name: github.compare
   slug: GITHUB_COMPARE_TWO_COMMITS
+  toolkit: github
   description: compare two refs (base...head) with the commits and changed files between them
   scopes: [repo]
   breadth: generic
@@ -182,6 +221,7 @@
 
 - name: github.list_pull_requests
   slug: GITHUB_LIST_PULL_REQUESTS
+  toolkit: github
   description: list pull requests on a repository, filterable by state and branch
   scopes: [repo]
   breadth: generic
@@ -190,6 +230,7 @@
 
 - name: github.list_pr_files
   slug: GITHUB_LIST_PULL_REQUESTS_FILES
+  toolkit: github
   description: list the files a pull request changes, with line counts and patches
   scopes: [repo]
   breadth: generic
@@ -198,6 +239,7 @@
 
 - name: github.list_pr_reviews
   slug: GITHUB_LIST_REVIEWS_FOR_A_PULL_REQUEST
+  toolkit: github
   description: list the reviews submitted on a pull request
   scopes: [repo]
   breadth: generic
@@ -206,6 +248,7 @@
 
 - name: github.search_issues
   slug: GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS
+  toolkit: github
   description: search issues and pull requests with GitHub qualifiers (repo:, author:, reviewed-by:, is:pr, created:)
   scopes: [repo]
   breadth: generic
@@ -214,6 +257,7 @@
 
 - name: linkedin.whoami
   slug: LINKEDIN_GET_MY_INFO
+  toolkit: linkedin
   description: read the connected LinkedIn member's id, name and headline (the author of their posts)
   scopes: [linkedin.profile]
   breadth: generic
@@ -222,6 +266,7 @@
 
 - name: linkedin.create_post
   slug: LINKEDIN_CREATE_LINKED_IN_POST
+  toolkit: linkedin
   description: publish a post on LinkedIn as the connected member or an organisation they manage
   scopes: [linkedin.w_member_social]
   breadth: generic