plimeor
- 13 skills
- 0 followers
- 6 hours ago last updated
- ▌ Code Plan · plimeor bundleWrite coding plans for implementation, debugging, refactoring, migrations, design parity, and long-running agent tasks. Use when drafting, refining, or validating a development plan, /goal prompt, implementation approach, scope and non-goals, work sequence, acceptance criteria, regression evidence, verification strategy, or stop condition. Near miss: use code-review to judge an existing diff, spec, or already-drafted plan.
- ▌ Agent Team · plimeor bundleRun a team of sub-agents under an orchestration blueprint: scout the surface, split it into atomic work units, dispatch them with baked context packets, have independent skeptic lanes attack every material claim, and synthesize one result with coverage and gaps named. Use for parallel coverage across independent evidence roots, inventorying an unknown-size surface, exhaustive review or audit, broad research needing cross-checked claims, codebase mapping, migration or sweep work, or adversarial critique of a decision — and whenever the user asks to fan out, delegate, run a team, or cross-check work across independent agents. Do not use for work the main agent should simply do itself, or for overlapping mutators without disjoint ownership or isolation.
- ▌ Entry Docs · plimeor bundleAuthor, refactor, or diagnose a repository's AGENTS.md (and CLAUDE.md) and/or README.md as complementary entrypoints. Use when writing, shrinking, splitting, or reviewing those files, when AGENTS.md is bloated or contradictory, or when a README cannot keep users out of the source. Near miss: not for SKILL.md authoring, ADRs, API reference as the primary artifact, CONTRIBUTING.md alone, blog posts, or implementing product features.
- ▌ Reconsider · plimeorUse before finalizing a non-trivial answer, recommendation, review, or decision, especially when shallow reasoning, stale context, a false frame, overconfidence, or transferring an outside framework or analogy onto the user's specific case could distort it, or when the user asks to reconsider, double-check, take a second look, or sanity-check. Not for one-line facts, simple commands, or mechanical formatting.
- ▌ Url Reader · plimeorRead the main content of a specific webpage URL when the user asks to summarize, inspect, cite, reference, or extract facts from that URL, including "read this", "look at this link", "based on this article", or equivalent reference requests. Owns URL retrieval safety for other skills that need webpage body content; not a broad web search tool.
- ▌ Code Review · plimeorReview concrete code plan drafts, specs, diffs, and implementation shapes, including parity audits of an implementation against an authoritative source or reference implementation. Use for code-review requests, exhaustive or line-by-line review requests, parity/alignment/completeness audits, serious code-plan design critique, and judging whether a proposed direction is sound. Near miss: use code-plan to create or revise plans; use code-design-review for a lightweight principles-only design assessment.
- ▌
- ▌ Writing Blog · plimeor bundleCreate, diagnose, outline, rewrite, or polish blog posts, articles, and newsletters. Use for drafting from notes, article outlines, structure and readability optimization, polishing rough notes toward publishable form, feedback on whether a draft reads well, or requests naming SCQA, the Pyramid Principle, or reader expectation management. Near miss: for raw reader-experience simulation with no writing advice, use writing-reader-feedback.
- ▌ Writing Humanizer · plimeorHumanize Chinese or English drafts. Use when the user asks to make writing less AI-like, more human, more natural, less generic, more authored, or when a draft feels over-polished, too symmetrical, generic, translated, or detached from the author's real judgment. Do not use as an AI-word blacklist, synonym-replacement pass, or fact-expansion pass, or to make technical writing casually chatty. Near miss: for structural revision or a blog-specific rewrite, use writing-blog.
- ▌ Code Design Review · plimeorAssess whether a design holds up against modern software-engineering principles: complexity and cognitive load, change economics, boundary correctness, and agent legibility. Use when the user asks whether a design, module boundary, API, data flow, design doc, or change shape is sound, holds up, or withstands scrutiny — a principle-based judgment, not a merge gate. Near miss: use code-review for exhaustive, coverage-accounted review of a diff, plan, or parity scope; use code-plan to create or revise plans.
- ▌ Code Test Strategy · plimeorDecide the smallest useful test strategy for a coding task without letting tests drive production-only complexity. Use when adding tests, choosing unit/integration/E2E level, reviewing mocks, doing TDD, or when an agent is about to add or modify tests.
- ▌ Create HTML Artifact · plimeor bundleProduce a single portable local HTML file as the final deliverable — a report, doc, dashboard, landing page, demo, tool, or presentation rendered as one .html that opens straight from disk. Use when the user asks for an HTML page/file/artifact saved locally, a visual or interactive deliverable as a standalone web page, or when porting content into one HTML file. Not for publishing or hosting a page online — the deliverable is a local file, never a URL — and not for multi-file web projects or apps with a build step.
- ▌ Writing Reader Feedback · plimeorSimulate a specified reader persona reading an article and report raw reading-experience feedback, not writing advice. Use when the user asks how a specific audience would experience a draft, whether readers can understand it, or wants reader simulation, reader-perspective feedback, or reader role-play. Near miss: for writing improvement, draft polishing, structural optimization, or a revision plan, use writing-blog.