Skip to content
Agentmart
Submit a tool

linkedin-safety-verification

Apply security, read-only, authorization, and same-layer verification rules to agent-operated LinkedIn workflows.

Skill by samihalawa

IndexedMIT
Write a review

Chalk Labs

Need help deploying linkedin-safety-verification?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/samihalawa-linkedin-safety-verification

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Apply security, read-only, authorization, and same-layer verification rules to agent-operated LinkedIn workflows. Use before account-visible changes, private request replay, broad captures, or provider AI tasks.

Use cases: security, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/linkedin-safety-verification

What's inside

Skill name
linkedin-safety-verification
Description
Apply security, read-only, authorization, and same-layer verification rules to agent-operated LinkedIn workflows. Use before account-visible changes, private request replay, broad captures, or provider AI tasks.
License
MIT
Instructions
16 lines in SKILL.md · view on GitHub

Files (3)

  • SKILL.md
  • openai.yaml · agents/
  • verification-gates.md · references/

SKILL.md (first lines)

# Safety and verification

1. Establish from the current request and authenticated account context that the user controls the account and requested the operation. Do this once for batch scope. Standing authorization eliminates agent-invented gates but never overrides the selected controller's action-time confirmation policy for sensitive-data entry, uploads, or submission.
2. Prefer `LINKEDIN_GODMODE_READ_ONLY=1` for inspection.
3. Keep capture scope narrow; bodies are opt-in.
4. Never expose cookies, authorization, API keys, CDP URLs, or task secrets.
5. Bulk work is allowed when the user authorizes the cohort, filters, or all matching items. Do not bypass challenges, evade limits, import/export cookies, schedule unrequested recurring campaigns, or add hidden out-of-scope loops.
6. Use the user-selected authenticated controller as authoritative. One controller's failure does not prove LinkedIn unavailable, and concurrent controllers must not read or write the same LinkedIn account.
7. For each write, execute once, verify it, and continue automatically. If the selected controller mandates action-time confirmation, prepare as far as allowed and ask once at the latest permitted moment with the exact role, destination, data, file, and action. Group only fully defined imminent actions; never ask early, vaguely, or again for an unchanged disclosed action.
8. After one literal account-wide quota or restriction state, preserve the queue and use independent authorized routes; recheck the blocked lane only after a reset or state-change signal.
9. Verify the failing or changed layer itself: browser state for UI, fresh API read for HTTP, provider status for hosted tasks.
10. State exact uncertainty when cloud providers or live LinkedIn behavior were not exercised. Do not infer exclusive causality from missing logs.

Use `references/verification-gates.md` for preflight and closure checks.

From samihalawa/linkedin-godmode-plugin, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 20, 2026 (2 months ago)
Last release
Aug 12, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from samihalawa

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get linkedin-safety-verification running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying linkedin-safety-verification?

CallGet help
Cite this page

linkedin-safety-verification skill. Agent Mart. https://agentmart.dev/skills/samihalawa-linkedin-safety-verification (last updated 2026-10-24)