Linkedin Hook Extractor
v1.0.0Analyze any viral LinkedIn post URL to identify its hook formula, structure, why it worked, and generate a blank template for your own writing.
⭐ 0· 33·0 current·0 all-time
bySergey Bulaev@sergebulaev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (teardown of viral LinkedIn posts) matches the instructions and included classification rules. The skill is instruction-only and does not ask for unrelated credentials, binaries, or config paths.
Instruction Scope
Runtime instructions are narrowly focused on parsing a LinkedIn URL, fetching the post text, extracting structured features, scoring formulas, and producing a template. However, the doc presumes availability of components not included in the bundle (e.g., lib.url_parser.parse_linkedin_url and a 'HarvestAPI' fetch mechanism) and refers to an external formulas file in another skill. Those assumptions are not declared or installed here and could cause the agent to reach out to external services or prompt the user for pasted content.
Install Mechanism
No install spec and no code files — nothing will be downloaded or written to disk by the skill itself. This minimizes install-time risk.
Credentials
The skill declares no required environment variables or credentials, which is appropriate for analyzing public posts. That said, the instruction to 'HarvestAPI preferred' implies use of an external scraping/fetch service that may require credentials or send data externally; those details are not declared in the skill.
Persistence & Privilege
The skill does not request permanent presence (always: false) and is user-invocable. It does not ask to modify other skills or system configuration.
Assessment
This skill appears coherent for analyzing public LinkedIn posts, but two practical checks before installing or using it: (1) Ask what 'HarvestAPI' refers to and whether it would cause the agent to call an external service (and if so, whether that service receives your post URLs or content). If HarvestAPI requires a token, confirm where that token would be stored and whether the skill would request it. (2) Verify whether your agent runtime provides the referenced helper 'lib.url_parser.parse_linkedin_url' or the related 'linkedin-post-writer' formula file; if not, expect the skill to prompt you to paste the post text. If you prefer not to have the agent contact external fetch services, use the fallback (paste the post text) when prompted.Like a lobster shell, security has layers — review code before you run it.
latestvk978cr3zndh217z85tcf2z8z9s84tfzvlinkedinvk978cr3zndh217z85tcf2z8z9s84tfzvmarketingvk978cr3zndh217z85tcf2z8z9s84tfzvsocial-mediavk978cr3zndh217z85tcf2z8z9s84tfzv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
