.claude/skills/linkedin-hack1 structural issue
- error: description exceeds the 1,024-character Agent Skills limit.
SKILL.md
Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Your agent crawls LinkedIn through the browser session you already have — profiles, search, connections, inbox, feed. No official API, no app review. Your cookies never leave the browser: API calls are a fetch() run inside the linkedin.com tab you shared (people-search navigates that tab to a LinkedIn search page and reads the results), and 1.2.1 DELETED the cookie-extraction, session-store and external-replay code from the package rather than leaving it switched off — there is no longer anything to store or steal…
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/linkedin-hackSKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/linkedin-hackSKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/linkedin-hackSKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @globalcaos/linkedin-hackclawhub inspect @globalcaos/linkedin-hack --version 1.2.2This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
keychain entry exists — checking would mean readkeychain_entry: 'not checked — looking it up would readThis is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:9be044c5d788d75abf18d72f21da9229148dbd5d96ddd691fdd19e30d6069c50scripts/linkedin.mjsSKILL.mdtests/cli.test.mjstests/origin.test.mjsCopied the published 1; Deleted keychainGet; Added a strict per-command --top range (out-of-range values are rejected); The relay must now be a literal loopback IP; TOKEN_FILE is no longer in OWNED_FILES; reserve() and bumpActivity() now run under an O_EXCL lock file (linkedin-activity; Those passages now say API calls are an in-tab fetch() and search people navigates the tab to a LinkedIn searc
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.
sha256:f80b9133860021657f8ff8fa7ff295bf1f3f29d6eefb35cb0672ce8654911998sha256:7b7df10bd155276595fee594107c265e53b3bd353fc4be9e6b37a63b742f8725