Stats
Actions
Tags
From in-optimize
Use when the user wants to design, scaffold, or extend a LinkedIn *post* cleaner that mirrors the comment cleaner's architecture. The src/ code for this surface does not yet exist — this skill is design notes and the slot layout for adding it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/in-optimize:postThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Status: **not implemented in `src/` yet.** This skill describes the slot layout to add it.
Status: not implemented in src/ yet. This skill describes the slot layout to add it.
URL: linkedin.com/in/me/recent-activity/all/ (own activity → posts/reposts/reactions).
Confirm with the user before writing code:
--since=<date> filter?src/postDetector.ts — DOM extraction, returns { id, urn, kind: 'post'|'repost'|'reaction', text }.src/postDelete.ts — clicks menu → "Delete post" → confirms. Different DOM from comments.src/selectors.ts — add a posts block alongside the existing comments block. Document in docs/selectors.md.src/runner.ts — extend, don't fork. Add --target=posts|comments dispatch on top of the existing loop. Reuse pace, scheduler, state.state/processed.json — namespace ids: post:<id>, comment:<id> to avoid collision.test/fixtures/posts.html — capture live, commit alongside the detector. Integration test loads it into Chromium and asserts the detector's output.
npx claudepluginhub cocodedk/in-optimizer --plugin in-optimizeGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.