[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M716ERVQMYJ1SA0VCQCMQCSS":3,"skill-same:01M716ERVQMYJ1SA0VCQCMQCSS":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M716ERVQMYJ1SA0VCQCMQCSS","linkedin-cli",null,"Use when automating LinkedIn via CLI: fetch profiles, search people\u002Fcompanies, send messages, manage connections, create posts, and Sales Navigator.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Flinkedin-cli\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"linkedin","cli","linkedin cli","community","2026","when","send","manage connections","posts","profiles","people","connections","manage","use","fetch","navigator","messages","search","create","safe","2026-11-10 10:12:30",false,"---\nname: linkedin-cli\ndescription: \"Use when automating LinkedIn via CLI: fetch profiles, search people\u002Fcompanies, send messages, manage connections, create posts, and Sales Navigator.\"\nrisk: safe\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n## When to Use\nUse this skill when you need to automate LinkedIn tasks such as profile fetching, connection management, or post creation via CLI, especially when integrated into automated workflows.\n\n# LinkedIn Skill\n\nYou have access to `linkedin` – a CLI tool for LinkedIn automation. Use it to fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and more.\n\nEach command sends a request to Linked API, which runs a real cloud browser to perform the action on LinkedIn. Operations are **not instant** – expect 30 seconds to several minutes depending on complexity.\n\nIf `linkedin` is not available, install it:\n\n```bash\nnpm install -g @linkedapi\u002Flinkedin-cli\n```\n\n## Authentication\n\nIf a command fails with exit code 2 (authentication error), ask the user to set up their account:\n\n1. Go to [app.linkedapi.io](https:\u002F\u002Fapp.linkedapi.io) and sign up or log in\n2. Connect their LinkedIn account\n3. Copy the **Linked API Token** and **Identification Token** from the dashboard\n\nOnce the user provides the tokens, run:\n\n```bash\nlinkedin setup --linked-api-token=TOKEN --identification-token=TOKEN\n```\n\n## When to Use\nUse this skill when you need to **orchestrate LinkedIn actions from scripts or an AI agent** instead of clicking through the web UI:\n\n- Building outreach, research, or recruiting workflows that rely on LinkedIn data and messaging.\n- Enriching leads or accounts by fetching people and company profiles in bulk.\n- Coordinating multi-step Sales Navigator or workflow runs where JSON output and exit codes are required.\n\nAlways respect LinkedIn’s terms of service, local regulations, and your organisation’s compliance policies when using automation against real accounts.\n\n## Global Flags\n\nAlways use `--json` and `-q` for machine-readable output:\n\n```bash\nlinkedin \u003Ccommand> --json -q\n```\n\n| Flag                    | Description                             |\n| ----------------------- | --------------------------------------- |\n| `--json`                | Structured JSON output                  |\n| `--quiet` \u002F `-q`        | Suppress stderr progress messages       |\n| `--fields name,url,...` | Select specific fields in output        |\n| `--no-color`            | Disable colors                          |\n| `--account \"Name\"`      | Use a specific account for this command |\n\n## Output Format\n\nSuccess:\n\n```json\n{ \"success\": true, \"data\": { \"name\": \"John Doe\", \"headline\": \"Engineer\" } }\n```\n\nError:\n\n```json\n{\n  \"success\": false,\n  \"error\": { \"type\": \"personNotFound\", \"message\": \"Person not found\" }\n}\n```\n\nExit code 0 means the API call succeeded – always check the `success` field for the action outcome. Non-zero exit codes indicate infrastructure errors:\n\n| Exit Code | Meaning                                                                                     |\n| --------- | ------------------------------------------------------------------------------------------- |\n| 0         | Success (check `success` field – action may have returned an error like \"person not found\") |\n| 1         | General\u002Funexpected error                                                                    |\n| 2         | Missing or invalid tokens                                                                   |\n| 3         | Subscription\u002Fplan required                                                                  |\n| 4         | LinkedIn account issue                                                                      |\n| 5         | Invalid arguments                                                                           |\n| 6         | Rate limited                                                                                |\n| 7         | Network error                                                                               |\n| 8         | Workflow timeout (workflowId returned for recovery)                                         |\n\n## Commands\n\n### Fetch a Person Profile\n\n```bash\nlinkedin person fetch \u003Curl> [flags] --json -q\n```\n\nOptional flags to include additional data:\n\n- `--experience` – work history\n- `--education` – education history\n- `--skills` – skills list\n- `--languages` – languages\n- `--posts` – recent posts (with `--posts-limit N`, `--posts-since TIMESTAMP`)\n- `--comments` – recent comments (with `--comments-limit N`, `--comments-since TIMESTAMP`)\n- `--reactions` – recent reactions (with `--reactions-limit N`, `--reactions-since TIMESTAMP`)\n\nOnly request additional data when needed – each flag increases execution time.\n\n```bash\n# Basic profile\nlinkedin person fetch https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --json -q\n\n# With experience and education\nlinkedin person fetch https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --experience --education --json -q\n\n# With last 5 posts\nlinkedin person fetch https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --posts --posts-limit 5 --json -q\n```\n\n### Search People\n\n```bash\nlinkedin person search [flags] --json -q\n```\n\n| Flag                   | Description                            |\n| ---------------------- | -------------------------------------- |\n| `--term`               | Search keyword or phrase               |\n| `--limit`              | Max results                            |\n| `--first-name`         | Filter by first name                   |\n| `--last-name`          | Filter by last name                    |\n| `--position`           | Filter by job position                 |\n| `--locations`          | Comma-separated locations              |\n| `--industries`         | Comma-separated industries             |\n| `--current-companies`  | Comma-separated current company names  |\n| `--previous-companies` | Comma-separated previous company names |\n| `--schools`            | Comma-separated school names           |\n\n```bash\nlinkedin person search --term \"product manager\" --locations \"San Francisco\" --json -q\nlinkedin person search --current-companies \"Google\" --position \"Engineer\" --limit 20 --json -q\n```\n\n### Fetch a Company\n\n```bash\nlinkedin company fetch \u003Curl> [flags] --json -q\n```\n\nOptional flags:\n\n- `--employees` – include employees\n- `--dms` – include decision makers\n- `--posts` – include company posts\n\nEmployee filters (require `--employees`):\n\n| Flag                     | Description                  |\n| ------------------------ | ---------------------------- |\n| `--employees-limit`      | Max employees to retrieve    |\n| `--employees-first-name` | Filter by first name         |\n| `--employees-last-name`  | Filter by last name          |\n| `--employees-position`   | Filter by position           |\n| `--employees-locations`  | Comma-separated locations    |\n| `--employees-industries` | Comma-separated industries   |\n| `--employees-schools`    | Comma-separated school names |\n\n| Flag            | Description                                        |\n| --------------- | -------------------------------------------------- |\n| `--dms-limit`   | Max decision makers to retrieve (requires `--dms`) |\n| `--posts-limit` | Max posts to retrieve (requires `--posts`)         |\n| `--posts-since` | Posts since ISO timestamp (requires `--posts`)     |\n\n```bash\n# Basic company info\nlinkedin company fetch https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --json -q\n\n# With employees filtered by position\nlinkedin company fetch https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --employees --employees-position \"Engineer\" --json -q\n\n# With decision makers and posts\nlinkedin company fetch https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --dms --posts --posts-limit 10 --json -q\n```\n\n### Search Companies\n\n```bash\nlinkedin company search [flags] --json -q\n```\n\n| Flag           | Description                                                                                                  |\n| -------------- | ------------------------------------------------------------------------------------------------------------ |\n| `--term`       | Search keyword                                                                                               |\n| `--limit`      | Max results                                                                                                  |\n| `--sizes`      | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |\n| `--locations`  | Comma-separated locations                                                                                    |\n| `--industries` | Comma-separated industries                                                                                   |\n\n```bash\nlinkedin company search --term \"fintech\" --sizes \"11-50,51-200\" --json -q\n```\n\n### Send a Message\n\n```bash\nlinkedin message send \u003Cperson-url> '\u003Ctext>' --json -q\n```\n\nText up to 1900 characters. Wrap the message in single quotes to avoid shell interpretation issues.\n\n```bash\nlinkedin message send https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername 'Hey, loved your latest post!' --json -q\n```\n\n### Get Conversation\n\n```bash\nlinkedin message get \u003Cperson-url> [--since TIMESTAMP] --json -q\n```\n\nThe first call for a conversation triggers a background sync and may take longer. Subsequent calls are faster.\n\n```bash\nlinkedin message get https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --json -q\nlinkedin message get https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --since 2024-01-15T10:30:00Z --json -q\n```\n\n### Connection Management\n\n#### Check connection status\n\n```bash\nlinkedin connection status \u003Curl> --json -q\n```\n\n#### Send connection request\n\n```bash\nlinkedin connection send \u003Curl> [--note 'text'] [--email user@example.com] --json -q\n```\n\n#### List connections\n\n```bash\nlinkedin connection list [flags] --json -q\n```\n\n| Flag                   | Description                                                                          |\n| ---------------------- | ------------------------------------------------------------------------------------ |\n| `--limit`              | Max connections to return                                                            |\n| `--since`              | Only connections made since ISO timestamp (only works when no filter flags are used) |\n| `--first-name`         | Filter by first name                                                                 |\n| `--last-name`          | Filter by last name                                                                  |\n| `--position`           | Filter by job position                                                               |\n| `--locations`          | Comma-separated locations                                                            |\n| `--industries`         | Comma-separated industries                                                           |\n| `--current-companies`  | Comma-separated current company names                                                |\n| `--previous-companies` | Comma-separated previous company names                                               |\n| `--schools`            | Comma-separated school names                                                         |\n\n```bash\nlinkedin connection list --limit 50 --json -q\nlinkedin connection list --current-companies \"Google\" --position \"Engineer\" --json -q\nlinkedin connection list --since 2024-01-01T00:00:00Z --json -q\n```\n\n#### List pending outgoing requests\n\n```bash\nlinkedin connection pending --json -q\n```\n\n#### Withdraw a pending request\n\n```bash\nlinkedin connection withdraw \u003Curl> [--no-unfollow] --json -q\n```\n\nBy default, withdrawing also unfollows the person. Use `--no-unfollow` to keep following.\n\n#### Remove a connection\n\n```bash\nlinkedin connection remove \u003Curl> --json -q\n```\n\n### Posts\n\n#### Fetch a post\n\n```bash\nlinkedin post fetch \u003Curl> [flags] --json -q\n```\n\n| Flag                 | Description                                                        |\n| -------------------- | ------------------------------------------------------------------ |\n| `--comments`         | Include comments                                                   |\n| `--reactions`        | Include reactions                                                  |\n| `--comments-limit`   | Max comments to retrieve (requires `--comments`)                   |\n| `--comments-sort`    | Sort order: `mostRelevant` or `mostRecent` (requires `--comments`) |\n| `--comments-replies` | Include replies to comments (requires `--comments`)                |\n| `--reactions-limit`  | Max reactions to retrieve (requires `--reactions`)                 |\n\n```bash\nlinkedin post fetch https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 --json -q\n\n# With comments sorted by most recent, including replies\nlinkedin post fetch https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 \\\n  --comments --comments-sort mostRecent --comments-replies --json -q\n```\n\n#### Create a post\n\n```bash\nlinkedin post create '\u003Ctext>' [flags] --json -q\n```\n\n| Flag            | Description                                                                                                        |\n| --------------- | ------------------------------------------------------------------------------------------------------------------ |\n| `--company-url` | Post on behalf of a company page (requires admin access)                                                           |\n| `--attachments` | Attachment as `url:type` or `url:type:name`. Types: `image`, `video`, `document`. Can be specified multiple times. |\n\nAttachment limits: up to 9 images, or 1 video, or 1 document. Cannot mix types.\n\n```bash\nlinkedin post create 'Excited to share our latest update!' --json -q\n\n# With a document\nlinkedin post create 'Our Q4 report' \\\n  --attachments \"https:\u002F\u002Fexample.com\u002Freport.pdf:document:Q4 Report\" --json -q\n\n# Post as a company\nlinkedin post create 'Company announcement' \\\n  --company-url https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --json -q\n```\n\n#### React to a post\n\n```bash\nlinkedin post react \u003Curl> --type \u003Creaction> [--company-url \u003Curl>] --json -q\n```\n\nReaction types: `like`, `love`, `support`, `celebrate`, `insightful`, `funny`.\n\n```bash\nlinkedin post react https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 --type like --json -q\n\n# React on behalf of a company\nlinkedin post react https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 --type celebrate \\\n  --company-url https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --json -q\n```\n\n#### Comment on a post\n\n```bash\nlinkedin post comment \u003Curl> '\u003Ctext>' [--company-url \u003Curl>] --json -q\n```\n\nText up to 1000 characters.\n\n```bash\nlinkedin post comment https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 'Great insights!' --json -q\n\n# Comment on behalf of a company\nlinkedin post comment https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 'Well said!' \\\n  --company-url https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --json -q\n```\n\n### Statistics\n\n```bash\n# Social Selling Index\nlinkedin stats ssi --json -q\n\n# Performance analytics (profile views, post impressions, search appearances)\nlinkedin stats performance --json -q\n\n# API usage for a date range\nlinkedin stats usage --start 2024-01-01T00:00:00Z --end 2024-01-31T00:00:00Z --json -q\n```\n\n### Sales Navigator\n\nRequires a LinkedIn Sales Navigator subscription. Uses hashed URLs for person\u002Fcompany lookups.\n\n#### Fetch person\n\n```bash\nlinkedin navigator person fetch \u003Chashed-url> --json -q\n```\n\n#### Search people\n\n```bash\nlinkedin navigator person search [flags] --json -q\n```\n\n| Flag                    | Description                                                                                 |\n| ----------------------- | ------------------------------------------------------------------------------------------- |\n| `--term`                | Search keyword or phrase                                                                    |\n| `--limit`               | Max results                                                                                 |\n| `--first-name`          | Filter by first name                                                                        |\n| `--last-name`           | Filter by last name                                                                         |\n| `--position`            | Filter by job position                                                                      |\n| `--locations`           | Comma-separated locations                                                                   |\n| `--industries`          | Comma-separated industries                                                                  |\n| `--current-companies`   | Comma-separated current company names                                                       |\n| `--previous-companies`  | Comma-separated previous company names                                                      |\n| `--schools`             | Comma-separated school names                                                                |\n| `--years-of-experience` | Comma-separated ranges: `lessThanOne`, `oneToTwo`, `threeToFive`, `sixToTen`, `moreThanTen` |\n\n```bash\nlinkedin navigator person search --term \"VP Marketing\" --locations \"United States\" --json -q\nlinkedin navigator person search --years-of-experience \"moreThanTen\" --position \"CEO\" --json -q\n```\n\n#### Fetch company\n\n```bash\nlinkedin navigator company fetch \u003Chashed-url> [flags] --json -q\n```\n\nOptional flags:\n\n- `--employees` – include employees\n- `--dms` – include decision makers\n\nEmployee filters (require `--employees`):\n\n| Flag                              | Description                                        |\n| --------------------------------- | -------------------------------------------------- |\n| `--employees-limit`               | Max employees to retrieve                          |\n| `--employees-first-name`          | Filter by first name                               |\n| `--employees-last-name`           | Filter by last name                                |\n| `--employees-positions`           | Comma-separated positions                          |\n| `--employees-locations`           | Comma-separated locations                          |\n| `--employees-industries`          | Comma-separated industries                         |\n| `--employees-schools`             | Comma-separated school names                       |\n| `--employees-years-of-experience` | Comma-separated experience ranges                  |\n| `--dms-limit`                     | Max decision makers to retrieve (requires `--dms`) |\n\n```bash\nlinkedin navigator company fetch https:\u002F\u002Fwww.linkedin.com\u002Fsales\u002Fcompany\u002F97ural --employees --dms --json -q\nlinkedin navigator company fetch https:\u002F\u002Fwww.linkedin.com\u002Fsales\u002Fcompany\u002F97ural \\\n  --employees --employees-positions \"Engineer,Designer\" --employees-locations \"Europe\" --json -q\n```\n\n#### Search companies\n\n```bash\nlinkedin navigator company search [flags] --json -q\n```\n\n| Flag            | Description                                                                                                  |\n| --------------- | ------------------------------------------------------------------------------------------------------------ |\n| `--term`        | Search keyword                                                                                               |\n| `--limit`       | Max results                                                                                                  |\n| `--sizes`       | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |\n| `--locations`   | Comma-separated locations                                                                                    |\n| `--industries`  | Comma-separated industries                                                                                   |\n| `--revenue-min` | Min annual revenue in M USD: `0`, `0.5`, `1`, `2.5`, `5`, `10`, `20`, `50`, `100`, `500`, `1000`             |\n| `--revenue-max` | Max annual revenue in M USD: `0.5`, `1`, `2.5`, `5`, `10`, `20`, `50`, `100`, `500`, `1000`, `1000+`         |\n\n```bash\nlinkedin navigator company search --term \"fintech\" --sizes \"11-50,51-200\" --json -q\nlinkedin navigator company search --revenue-min 10 --revenue-max 100 --locations \"United States\" --json -q\n```\n\n#### Send InMail\n\n```bash\nlinkedin navigator message send \u003Cperson-url> '\u003Ctext>' --subject '\u003Csubject>' --json -q\n```\n\nText up to 1900 characters. Subject up to 80 characters.\n\n```bash\nlinkedin navigator message send https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername \\\n  'Would love to chat about API integrations' --subject 'Partnership Opportunity' --json -q\n```\n\n#### Get Sales Navigator conversation\n\n```bash\nlinkedin navigator message get \u003Cperson-url> [--since TIMESTAMP] --json -q\n```\n\n### Custom Workflows\n\nExecute a custom workflow definition from a file, stdin, or inline:\n\n```bash\n# From file\nlinkedin workflow run --file workflow.json --json -q\n\n# From stdin\ncat workflow.json | linkedin workflow run --json -q\n\n# Inline\necho '{\"actions\":[...]}' | linkedin workflow run --json -q\n```\n\nCheck workflow status or wait for completion:\n\n```bash\nlinkedin workflow status \u003Cid> --json -q\nlinkedin workflow status \u003Cid> --wait --json -q\n```\n\nSee [Building Workflows](https:\u002F\u002Flinkedapi.io\u002Fdocs\u002Fbuilding-workflows\u002F) for the workflow JSON schema.\n\n### Account Management\n\n```bash\nlinkedin account list                            # List accounts (* = active)\nlinkedin account switch \"Name\"                   # Switch active account\nlinkedin account rename \"Name\" --name \"New Name\" # Rename account\nlinkedin reset                                   # Remove active account\nlinkedin reset --all                             # Remove all accounts\n```\n\n## Important Behavior\n\n- **Sequential execution.** All operations for an account run one at a time. Multiple requests queue up.\n- **Not instant.** A real browser navigates LinkedIn – expect 30 seconds to several minutes per operation.\n- **Timestamps in UTC.** All dates and times are in UTC.\n- **Single quotes for text arguments.** Use single quotes around message text, post text, and comments to avoid shell interpretation issues with special characters.\n- **Action limits.** Per-account limits are configurable on the platform. A `limitExceeded` error means the limit was reached.\n- **URL normalization.** All LinkedIn URLs in responses are normalized to `https:\u002F\u002Fwww.linkedin.com\u002F...` format without trailing slashes.\n- **Null fields.** Fields that are unavailable are returned as `null` or `[]`, not omitted.\n","## When to Use\nUse this skill when you need to automate LinkedIn tasks such as profile fetching, connection management, or post creation via CLI, especially when integrated into automated workflows.\n\n# LinkedIn Skill\n\nYou have access to `linkedin` – a CLI tool for LinkedIn automation. Use it to fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and more.\n\nEach command sends a request to Linked API, which runs a real cloud browser to perform the action on LinkedIn. Operations are **not instant** – expect 30 seconds to several minutes depending on complexity.\n\nIf `linkedin` is not available, install it:\n\n```bash\nnpm install -g @linkedapi\u002Flinkedin-cli\n```\n\n## Authentication\n\nIf a command fails with exit code 2 (authentication error), ask the user to set up their account:\n\n1. Go to [app.linkedapi.io](https:\u002F\u002Fapp.linkedapi.io) and sign up or log in\n2. Connect their LinkedIn account\n3. Copy the **Linked API Token** and **Identification Token** from the dashboard\n\nOnce the user provides the tokens, run:\n\n```bash\nlinkedin setup --linked-api-token=TOKEN --identification-token=TOKEN\n```\n\n## When to Use\nUse this skill when you need to **orchestrate LinkedIn actions from scripts or an AI agent** instead of clicking through the web UI:\n\n- Building outreach, research, or recruiting workflows that rely on LinkedIn data and messaging.\n- Enriching leads or accounts by fetching people and company profiles in bulk.\n- Coordinating multi-step Sales Navigator or workflow runs where JSON output and exit codes are required.\n\nAlways respect LinkedIn’s terms of service, local regulations, and your organisation’s compliance policies when using automation against real accounts.\n\n## Global Flags\n\nAlways use `--json` and `-q` for machine-readable output:\n\n```bash\nlinkedin \u003Ccommand> --json -q\n```\n\n| Flag                    | Description                             |\n| ----------------------- | --------------------------------------- |\n| `--json`                | Structured JSON output                  |\n| `--quiet` \u002F `-q`        | Suppress stderr progress messages       |\n| `--fields name,url,...` | Select specific fields in output        |\n| `--no-color`            | Disable colors                          |\n| `--account \"Name\"`      | Use a specific account for this command |\n\n## Output Format\n\nSuccess:\n\n```json\n{ \"success\": true, \"data\": { \"name\": \"John Doe\", \"headline\": \"Engineer\" } }\n```\n\nError:\n\n```json\n{\n  \"success\": false,\n  \"error\": { \"type\": \"personNotFound\", \"message\": \"Person not found\" }\n}\n```\n\nExit code 0 means the API call succeeded – always check the `success` field for the action outcome. Non-zero exit codes indicate infrastructure errors:\n\n| Exit Code | Meaning                                                                                     |\n| --------- | ------------------------------------------------------------------------------------------- |\n| 0         | Success (check `success` field – action may have returned an error like \"person not found\") |\n| 1         | General\u002Funexpected error                                                                    |\n| 2         | Missing or invalid tokens                                                                   |\n| 3         | Subscription\u002Fplan required                                                                  |\n| 4         | LinkedIn account issue                                                                      |\n| 5         | Invalid arguments                                                                           |\n| 6         | Rate limited                                                                                |\n| 7         | Network error                                                                               |\n| 8         | Workflow timeout (workflowId returned for recovery)                                         |\n\n## Commands\n\n### Fetch a Person Profile\n\n```bash\nlinkedin person fetch \u003Curl> [flags] --json -q\n```\n\nOptional flags to include additional data:\n\n- `--experience` – work history\n- `--education` – education history\n- `--skills` – skills list\n- `--languages` – languages\n- `--posts` – recent posts (with `--posts-limit N`, `--posts-since TIMESTAMP`)\n- `--comments` – recent comments (with `--comments-limit N`, `--comments-since TIMESTAMP`)\n- `--reactions` – recent reactions (with `--reactions-limit N`, `--reactions-since TIMESTAMP`)\n\nOnly request additional data when needed – each flag increases execution time.\n\n```bash\n# Basic profile\nlinkedin person fetch https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --json -q\n\n# With experience and education\nlinkedin person fetch https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --experience --education --json -q\n\n# With last 5 posts\nlinkedin person fetch https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --posts --posts-limit 5 --json -q\n```\n\n### Search People\n\n```bash\nlinkedin person search [flags] --json -q\n```\n\n| Flag                   | Description                            |\n| ---------------------- | -------------------------------------- |\n| `--term`               | Search keyword or phrase               |\n| `--limit`              | Max results                            |\n| `--first-name`         | Filter by first name                   |\n| `--last-name`          | Filter by last name                    |\n| `--position`           | Filter by job position                 |\n| `--locations`          | Comma-separated locations              |\n| `--industries`         | Comma-separated industries             |\n| `--current-companies`  | Comma-separated current company names  |\n| `--previous-companies` | Comma-separated previous company names |\n| `--schools`            | Comma-separated school names           |\n\n```bash\nlinkedin person search --term \"product manager\" --locations \"San Francisco\" --json -q\nlinkedin person search --current-companies \"Google\" --position \"Engineer\" --limit 20 --json -q\n```\n\n### Fetch a Company\n\n```bash\nlinkedin company fetch \u003Curl> [flags] --json -q\n```\n\nOptional flags:\n\n- `--employees` – include employees\n- `--dms` – include decision makers\n- `--posts` – include company posts\n\nEmployee filters (require `--employees`):\n\n| Flag                     | Description                  |\n| ------------------------ | ---------------------------- |\n| `--employees-limit`      | Max employees to retrieve    |\n| `--employees-first-name` | Filter by first name         |\n| `--employees-last-name`  | Filter by last name          |\n| `--employees-position`   | Filter by position           |\n| `--employees-locations`  | Comma-separated locations    |\n| `--employees-industries` | Comma-separated industries   |\n| `--employees-schools`    | Comma-separated school names |\n\n| Flag            | Description                                        |\n| --------------- | -------------------------------------------------- |\n| `--dms-limit`   | Max decision makers to retrieve (requires `--dms`) |\n| `--posts-limit` | Max posts to retrieve (requires `--posts`)         |\n| `--posts-since` | Posts since ISO timestamp (requires `--posts`)     |\n\n```bash\n# Basic company info\nlinkedin company fetch https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --json -q\n\n# With employees filtered by position\nlinkedin company fetch https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --employees --employees-position \"Engineer\" --json -q\n\n# With decision makers and posts\nlinkedin company fetch https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --dms --posts --posts-limit 10 --json -q\n```\n\n### Search Companies\n\n```bash\nlinkedin company search [flags] --json -q\n```\n\n| Flag           | Description                                                                                                  |\n| -------------- | ------------------------------------------------------------------------------------------------------------ |\n| `--term`       | Search keyword                                                                                               |\n| `--limit`      | Max results                                                                                                  |\n| `--sizes`      | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |\n| `--locations`  | Comma-separated locations                                                                                    |\n| `--industries` | Comma-separated industries                                                                                   |\n\n```bash\nlinkedin company search --term \"fintech\" --sizes \"11-50,51-200\" --json -q\n```\n\n### Send a Message\n\n```bash\nlinkedin message send \u003Cperson-url> '\u003Ctext>' --json -q\n```\n\nText up to 1900 characters. Wrap the message in single quotes to avoid shell interpretation issues.\n\n```bash\nlinkedin message send https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername 'Hey, loved your latest post!' --json -q\n```\n\n### Get Conversation\n\n```bash\nlinkedin message get \u003Cperson-url> [--since TIMESTAMP] --json -q\n```\n\nThe first call for a conversation triggers a background sync and may take longer. Subsequent calls are faster.\n\n```bash\nlinkedin message get https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --json -q\nlinkedin message get https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername --since 2024-01-15T10:30:00Z --json -q\n```\n\n### Connection Management\n\n#### Check connection status\n\n```bash\nlinkedin connection status \u003Curl> --json -q\n```\n\n#### Send connection request\n\n```bash\nlinkedin connection send \u003Curl> [--note 'text'] [--email user@example.com] --json -q\n```\n\n#### List connections\n\n```bash\nlinkedin connection list [flags] --json -q\n```\n\n| Flag                   | Description                                                                          |\n| ---------------------- | ------------------------------------------------------------------------------------ |\n| `--limit`              | Max connections to return                                                            |\n| `--since`              | Only connections made since ISO timestamp (only works when no filter flags are used) |\n| `--first-name`         | Filter by first name                                                                 |\n| `--last-name`          | Filter by last name                                                                  |\n| `--position`           | Filter by job position                                                               |\n| `--locations`          | Comma-separated locations                                                            |\n| `--industries`         | Comma-separated industries                                                           |\n| `--current-companies`  | Comma-separated current company names                                                |\n| `--previous-companies` | Comma-separated previous company names                                               |\n| `--schools`            | Comma-separated school names                                                         |\n\n```bash\nlinkedin connection list --limit 50 --json -q\nlinkedin connection list --current-companies \"Google\" --position \"Engineer\" --json -q\nlinkedin connection list --since 2024-01-01T00:00:00Z --json -q\n```\n\n#### List pending outgoing requests\n\n```bash\nlinkedin connection pending --json -q\n```\n\n#### Withdraw a pending request\n\n```bash\nlinkedin connection withdraw \u003Curl> [--no-unfollow] --json -q\n```\n\nBy default, withdrawing also unfollows the person. Use `--no-unfollow` to keep following.\n\n#### Remove a connection\n\n```bash\nlinkedin connection remove \u003Curl> --json -q\n```\n\n### Posts\n\n#### Fetch a post\n\n```bash\nlinkedin post fetch \u003Curl> [flags] --json -q\n```\n\n| Flag                 | Description                                                        |\n| -------------------- | ------------------------------------------------------------------ |\n| `--comments`         | Include comments                                                   |\n| `--reactions`        | Include reactions                                                  |\n| `--comments-limit`   | Max comments to retrieve (requires `--comments`)                   |\n| `--comments-sort`    | Sort order: `mostRelevant` or `mostRecent` (requires `--comments`) |\n| `--comments-replies` | Include replies to comments (requires `--comments`)                |\n| `--reactions-limit`  | Max reactions to retrieve (requires `--reactions`)                 |\n\n```bash\nlinkedin post fetch https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 --json -q\n\n# With comments sorted by most recent, including replies\nlinkedin post fetch https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 \\\n  --comments --comments-sort mostRecent --comments-replies --json -q\n```\n\n#### Create a post\n\n```bash\nlinkedin post create '\u003Ctext>' [flags] --json -q\n```\n\n| Flag            | Description                                                                                                        |\n| --------------- | ------------------------------------------------------------------------------------------------------------------ |\n| `--company-url` | Post on behalf of a company page (requires admin access)                                                           |\n| `--attachments` | Attachment as `url:type` or `url:type:name`. Types: `image`, `video`, `document`. Can be specified multiple times. |\n\nAttachment limits: up to 9 images, or 1 video, or 1 document. Cannot mix types.\n\n```bash\nlinkedin post create 'Excited to share our latest update!' --json -q\n\n# With a document\nlinkedin post create 'Our Q4 report' \\\n  --attachments \"https:\u002F\u002Fexample.com\u002Freport.pdf:document:Q4 Report\" --json -q\n\n# Post as a company\nlinkedin post create 'Company announcement' \\\n  --company-url https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --json -q\n```\n\n#### React to a post\n\n```bash\nlinkedin post react \u003Curl> --type \u003Creaction> [--company-url \u003Curl>] --json -q\n```\n\nReaction types: `like`, `love`, `support`, `celebrate`, `insightful`, `funny`.\n\n```bash\nlinkedin post react https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 --type like --json -q\n\n# React on behalf of a company\nlinkedin post react https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 --type celebrate \\\n  --company-url https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --json -q\n```\n\n#### Comment on a post\n\n```bash\nlinkedin post comment \u003Curl> '\u003Ctext>' [--company-url \u003Curl>] --json -q\n```\n\nText up to 1000 characters.\n\n```bash\nlinkedin post comment https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 'Great insights!' --json -q\n\n# Comment on behalf of a company\nlinkedin post comment https:\u002F\u002Fwww.linkedin.com\u002Fposts\u002Fusername_activity-123 'Well said!' \\\n  --company-url https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fname --json -q\n```\n\n### Statistics\n\n```bash\n# Social Selling Index\nlinkedin stats ssi --json -q\n\n# Performance analytics (profile views, post impressions, search appearances)\nlinkedin stats performance --json -q\n\n# API usage for a date range\nlinkedin stats usage --start 2024-01-01T00:00:00Z --end 2024-01-31T00:00:00Z --json -q\n```\n\n### Sales Navigator\n\nRequires a LinkedIn Sales Navigator subscription. Uses hashed URLs for person\u002Fcompany lookups.\n\n#### Fetch person\n\n```bash\nlinkedin navigator person fetch \u003Chashed-url> --json -q\n```\n\n#### Search people\n\n```bash\nlinkedin navigator person search [flags] --json -q\n```\n\n| Flag                    | Description                                                                                 |\n| ----------------------- | ------------------------------------------------------------------------------------------- |\n| `--term`                | Search keyword or phrase                                                                    |\n| `--limit`               | Max results                                                                                 |\n| `--first-name`          | Filter by first name                                                                        |\n| `--last-name`           | Filter by last name                                                                         |\n| `--position`            | Filter by job position                                                                      |\n| `--locations`           | Comma-separated locations                                                                   |\n| `--industries`          | Comma-separated industries                                                                  |\n| `--current-companies`   | Comma-separated current company names                                                       |\n| `--previous-companies`  | Comma-separated previous company names                                                      |\n| `--schools`             | Comma-separated school names                                                                |\n| `--years-of-experience` | Comma-separated ranges: `lessThanOne`, `oneToTwo`, `threeToFive`, `sixToTen`, `moreThanTen` |\n\n```bash\nlinkedin navigator person search --term \"VP Marketing\" --locations \"United States\" --json -q\nlinkedin navigator person search --years-of-experience \"moreThanTen\" --position \"CEO\" --json -q\n```\n\n#### Fetch company\n\n```bash\nlinkedin navigator company fetch \u003Chashed-url> [flags] --json -q\n```\n\nOptional flags:\n\n- `--employees` – include employees\n- `--dms` – include decision makers\n\nEmployee filters (require `--employees`):\n\n| Flag                              | Description                                        |\n| --------------------------------- | -------------------------------------------------- |\n| `--employees-limit`               | Max employees to retrieve                          |\n| `--employees-first-name`          | Filter by first name                               |\n| `--employees-last-name`           | Filter by last name                                |\n| `--employees-positions`           | Comma-separated positions                          |\n| `--employees-locations`           | Comma-separated locations                          |\n| `--employees-industries`          | Comma-separated industries                         |\n| `--employees-schools`             | Comma-separated school names                       |\n| `--employees-years-of-experience` | Comma-separated experience ranges                  |\n| `--dms-limit`                     | Max decision makers to retrieve (requires `--dms`) |\n\n```bash\nlinkedin navigator company fetch https:\u002F\u002Fwww.linkedin.com\u002Fsales\u002Fcompany\u002F97ural --employees --dms --json -q\nlinkedin navigator company fetch https:\u002F\u002Fwww.linkedin.com\u002Fsales\u002Fcompany\u002F97ural \\\n  --employees --employees-positions \"Engineer,Designer\" --employees-locations \"Europe\" --json -q\n```\n\n#### Search companies\n\n```bash\nlinkedin navigator company search [flags] --json -q\n```\n\n| Flag            | Description                                                                                                  |\n| --------------- | ------------------------------------------------------------------------------------------------------------ |\n| `--term`        | Search keyword                                                                                               |\n| `--limit`       | Max results                                                                                                  |\n| `--sizes`       | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |\n| `--locations`   | Comma-separated locations                                                                                    |\n| `--industries`  | Comma-separated industries                                                                                   |\n| `--revenue-min` | Min annual revenue in M USD: `0`, `0.5`, `1`, `2.5`, `5`, `10`, `20`, `50`, `100`, `500`, `1000`             |\n| `--revenue-max` | Max annual revenue in M USD: `0.5`, `1`, `2.5`, `5`, `10`, `20`, `50`, `100`, `500`, `1000`, `1000+`         |\n\n```bash\nlinkedin navigator company search --term \"fintech\" --sizes \"11-50,51-200\" --json -q\nlinkedin navigator company search --revenue-min 10 --revenue-max 100 --locations \"United States\" --json -q\n```\n\n#### Send InMail\n\n```bash\nlinkedin navigator message send \u003Cperson-url> '\u003Ctext>' --subject '\u003Csubject>' --json -q\n```\n\nText up to 1900 characters. Subject up to 80 characters.\n\n```bash\nlinkedin navigator message send https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fusername \\\n  'Would love to chat about API integrations' --subject 'Partnership Opportunity' --json -q\n```\n\n#### Get Sales Navigator conversation\n\n```bash\nlinkedin navigator message get \u003Cperson-url> [--since TIMESTAMP] --json -q\n```\n\n### Custom Workflows\n\nExecute a custom workflow definition from a file, stdin, or inline:\n\n```bash\n# From file\nlinkedin workflow run --file workflow.json --json -q\n\n# From stdin\ncat workflow.json | linkedin workflow run --json -q\n\n# Inline\necho '{\"actions\":[...]}' | linkedin workflow run --json -q\n```\n\nCheck workflow status or wait for completion:\n\n```bash\nlinkedin workflow status \u003Cid> --json -q\nlinkedin workflow status \u003Cid> --wait --json -q\n```\n\nSee [Building Workflows](https:\u002F\u002Flinkedapi.io\u002Fdocs\u002Fbuilding-workflows\u002F) for the workflow JSON schema.\n\n### Account Management\n\n```bash\nlinkedin account list                            # List accounts (* = active)\nlinkedin account switch \"Name\"                   # Switch active account\nlinkedin account rename \"Name\" --name \"New Name\" # Rename account\nlinkedin reset                                   # Remove active account\nlinkedin reset --all                             # Remove all accounts\n```\n\n## Important Behavior\n\n- **Sequential execution.** All operations for an account run one at a time. Multiple requests queue up.\n- **Not instant.** A real browser navigates LinkedIn – expect 30 seconds to several minutes per operation.\n- **Timestamps in UTC.** All dates and times are in UTC.\n- **Single quotes for text arguments.** Use single quotes around message text, post text, and comments to avoid shell interpretation issues with special characters.\n- **Action limits.** Per-account limits are configurable on the platform. A `limitExceeded` error means the limit was reached.\n- **URL normalization.** All LinkedIn URLs in responses are normalized to `https:\u002F\u002Fwww.linkedin.com\u002F...` format without trailing slashes.\n- **Null fields.** Fields that are unavailable are returned as `null` or `[]`, not omitted.\n",{"name":5,"risk":38,"source":22,"date_added":44,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcursor\u002Flinkedin-cli","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill linkedin-cli",{"tool":57,"command":58},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill linkedin-cli",{"tool":60,"command":61},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill linkedin-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Flinkedin-cli\u002FSKILL.md",true,[],[66,88,113,123,136,154],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":39},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[78,79,36,80,81,82,83,84,85,86,33,87],"wechat search","wechat","capabilities","openclaw","design","web search","compliance","web","official","with",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":39},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[95,96,97,98,99,100,36,101,102,103,104,24,105,106,107,108,109,110,111,112],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","brew","live","data","google","install","read","across","api",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":39},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[120,121,95,105,106,107,108,99,36,110,122,111,112,24,103,102,101,109,100,98],"trend radar","radar","pulse",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":39},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[130,131,132,133,134,135],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":147,"publishedAt":39},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[138,85,148,20,149,87,105,150,151,152,97,153,109],"Audio","youtube","images","https","files","pdfs",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":39},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[156,161,162,163,109,164,151,165,166,167,168,169],"status","play","go","latest","github","discover","control","cmd","volume"]