Security audit
Security checks across malware telemetry and agentic risk
This appears to be a genuine LinkedIn Company Page publishing skill, but it requests broader LinkedIn organization-admin permission than its posting workflow needs and handles long-lived tokens in a risky way.
Install only if you are comfortable granting this skill LinkedIn Company Page publishing power. Before authorizing OAuth, review the consent screen and avoid approving organization-admin permissions unless you specifically need them. Store tokens in a secure secret manager or tightly permissioned local file, revoke/rotate them if exposed, and use `--dry-run` plus explicit human approval before any live post.
- **Personal token limit**: roughly 100 calls/day/member. Respect this when building schedulers. - **Scope required**: `w_organization_social`. The authenticating user must be an admin of the Company Page — being an employee is not enough. - **Post character limit**: 3,000. The API returns HTTP 422 if exceeded. The library checks locally before calling so the failure is cheaper. - **Access token lifetime**: 60 days. Refresh tokens last 365 days and can be used to mint new access tokens without re-prompting the user. `get_token.py` saves both. ## What LinkedIn's API cannot do (as of 2026)
- **Personal token limit**: roughly 100 calls/day/member. Respect this when building schedulers. - **Scope required**: `w_organization_social`. The authenticating user must be an admin of the Company Page — being an employee is not enough. - **Post character limit**: 3,000. The API returns HTTP 422 if exceeded. The library checks locally before calling so the failure is cheaper. - **Access token lifetime**: 60 days. Refresh tokens last 365 days and can be used to mint new access tokens without re-prompting the user. `get_token.py` saves both. ## What LinkedIn's API cannot do (as of 2026)
67/67 vendors flagged this skill as clean.
No suspicious patterns detected.
