Linkedin Comment Drafter

Key things to check before installing or enabling this skill: - Confirm how posting is performed: ask the publisher what 'Publora' is, where posts go, and whether the skill will ever post without an explicit, per-use approval. The SKILL.md refers to PUBLORA_API_KEY but the registry metadata does not declare it — don't provide credentials until you verify the backend and its privacy/security policies. - Verify the existence and provenance of the referenced libraries (lib.url_parser, lib.PubloraClient, lib.approval, and the HarvestAPI path). These look like internal helpers; if they aren't present the skill should fall back to manual mode only. - Prefer to run this skill in manual mode (copy-paste drafts) until you can inspect the code that implements the Publora/custom-poster backends. Ensure any custom poster command you configure is safe and sanitized (it will receive the draft text and target URL as args). - Be cautious about the HarvestAPI/internal path: it suggests the skill can access corporate/personal knowledge stores if available. Understand what data would be read and whether that access is permitted. - Ask the publisher for source code or a homepage. Instruction-only skills can be helpful but when they reference unspecified credentials and internal modules, that inconsistency should be resolved before granting any secrets or allowing automated posting.