neeeophytee
- 47 skills
- 0 followers
- 6 hours ago last updated
- ▌ Audit Provenance · neeeophytee bundleAnswer the five provenance questions for a single asset in one pass - was provenance located, verified, and trusted, was the scan complete, and what remains unknown. Use when a user asks for an overall provenance verdict on a file and does not want to orchestrate the individual analyzers themselves.
- ▌ Check AI Transparency · neeeophytee bundleReview a structured record of AI-generated outputs for provenance evidence, human-readable disclosure, model identification, and documented edits. Use when preparing for publication or policy review and teams need gaps and next actions without a legal conclusion.
- ▌ Detect Text Watermark · neeeophytee bundleRun every available text-provenance detector over a document or string and report per-detector states, including hidden Unicode channels and detached C2PA manifests. Use when a user asks whether text carries an AI watermark, contains invisible or smuggled characters, or is safe to feed into an agent pipeline.
- ▌ Audit Metadata Privacy · neeeophytee bundleAudit supported metadata surfaces in images, SVG, PDF, and OOXML assets for privacy signals such as GPS, author, device, software, comments, and timestamps. Use when preparing a public release and metadata exposure must be assessed without altering or invalidating provenance.
- ▌ Map Provenance Survival · neeeophytee bundleCompare an original asset with resized, converted, uploaded, or downloaded derivatives and produce a JSON, Markdown, or HTML provenance-survival report. Use when testing whether a CMS, image optimizer, social network, editor, screenshot, watermark-removal tool, or publishing workflow preserves Content Credentials.
- ▌ Inspect Content Provenance · neeeophytee bundleInspect local files or text for observable provenance metadata, possible C2PA markers, hashes, and text control characters. Use when a user asks whether an asset contains Content Credentials, an AI mark, provenance metadata, or suspicious invisible characters and a cautious inventory is needed before cryptographic verification.
- ▌ Verify Content Credentials · neeeophytee bundleVerify C2PA Content Credentials in a local asset with the official c2patool, separating manifest presence, cryptographic integrity, and signer trust. Use when a user needs defensible validation instead of byte-marker guesses, including offline and unavailable-verifier cases.
- ▌ Context Diet · neeeophyteeCut agent token spend by shrinking what enters the context window. Index the repo or corpus once and query it instead of re-reading files on every question. Use when the user complains their coding agent burns tokens, the context fills up fast, the same files get read repeatedly, or the bill scales with conversation length.
- ▌ Model Bakeoff · neeeophyteeChoose a model with evidence by running the few prompts that actually matter across candidate models inside a free tier's caps, picking by a stated criterion. Use when the user asks "which model should I use", wants to evaluate a newly launched model, or is choosing between models for a specific task.
- ▌ Tested Fallback · neeeophyteePin an open-weights fallback model with a tested-on date and real smoke prompts, so a pulled or deprecated model is a two-minute config swap instead of a lost week. Use when the user worries a model could vanish or be deprecated, builds anything important on one model, or asks about model failover and resilience.
- ▌ Cheap Swap Guard · neeeophyteeBefore swapping any workload to a cheaper model, declare the cases the premium model still dominates and prove they keep routing to premium. Use when the user wants to "just switch" to a cheaper model (text, image, or video), or asks whether a cheap model is good enough to replace an expensive one.
- ▌ Free Model Triage · neeeophyteeRoute high-volume, low-stakes triage (reading piles, inbox summaries, needs-reply flags) to a free model with a strict output schema. Use when the user wants one-line summaries of many items cheaply, asks to triage email, articles, or reports with AI, or wants to decide what's worth reading without paying premium rates for it.
- ▌ Advisor Call Budget · neeeophyteeEnforce a hard cap and a drift-check when a cheap executor model consults an expensive advisor model, and compute the effective cost from actual call counts instead of a benchmark's assumed rate. Use when the user adopts the advisor or orchestrator pattern, pairs a cheap model with an expensive reviewer, or quotes a benchmark discount like "63% of the price".
- ▌ Free Tier Batch Plan · neeeophyteeSize a big one-time batch job against a free tier's rate limit and token budget BEFORE starting it, with a proven wall-clock ETA. Use when the user wants to label a dataset, summarize an archive, or process a large backlog for free (or on a tiny rate limit), or asks "will this finish overnight?"
- ▌ Token Receipts Audit · neeeophyteeAttribute AI usage by tokens AND dollars so a high-volume cheap model is never mistaken for the expensive one. Use when the user asks where their AI spend actually goes, why the bill is high, which model is costing the most, or wants a usage audit across agents and models.
- ▌ Reasoning Effort Throttle · neeeophyteeStop paying for deep reasoning on easy turns by setting a modest default reasoning effort and escalating per task. Use when the user runs a reasoning model in an agent and the bill is dominated by output or thinking tokens, or asks about reasoning_effort, thinking budgets, or why a cheap model is still expensive to run.
- ▌ Route Cheap Escalate Hard · neeeophyteeCut LLM spend by routing bulk work to a cheap model and escalating only the hard turns to a premium one. Use when the user says their AI bill is too high, asks to "use a cheaper model", or wants two-tier model routing without losing quality on the hard tasks.
- ▌ Change Quiz · neeeophyteeAfter a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.
- ▌ Interview Me · neeeophyteeInterview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.
- ▌ Context Audit · neeeophyteeAudit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.
- ▌ Blindspot Pass · neeeophyteeSurface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."
- ▌ Pitch Packager · neeeophyteePackage a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast. Use when the user needs buy-in, a review, or a shareable summary of what was built and why.
- ▌ Reference Hunt · neeeophyteeUse existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.
- ▌ Assumption Test · neeeophyteeTest a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.
- ▌ Test Blindspots · neeeophyteeFind consequential behavior that a passing test suite does not establish, using focused exploratory checks. Use when the user asks what green tests miss or wants confidence in test coverage for a specific change. Not a general code review, routine test run, or debugging workflow for an already failing test.
- ▌ Implementation Plan · neeeophyteeWrite an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.
- ▌ Implementation Notes · neeeophyteeKeep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.
- ▌ Brainstorm Prototypes · neeeophyteeGenerate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.
- ▌ Agent Interface Design · neeeophyteeDesign tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.
- ▌ Progressive Disclosure · neeeophyteeSplit an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.
- ▌ Govuk · neeeophytee bundleDraft, rewrite, or audit plain-language public-service content using an independently expressed interpretation of GOV.UK content design. Use for eligibility pages, government guidance, policy explanations, forms, transactions, public notices, and content that must help people make a decision or complete a service task.
- ▌ 18f Content · neeeophytee bundleDraft, rewrite, or audit inclusive US digital-government content using an independently expressed interpretation of the 18F Content Guide. Use for public-service websites, forms, applications, transactional messages, help content, notices, and government digital experiences that should help people complete a task with minimal bureaucratic burden.
- ▌ Github Docs · neeeophytee bundleDraft, rewrite, or audit approachable developer product documentation using an independently expressed interpretation of the GitHub Docs style. Use for product workflows, how-to guides, conceptual overviews, troubleshooting, security guidance, and documentation that should move developers from prerequisites to a verified outcome.
- ▌ Gitlab Docs · neeeophytee bundleDraft, rewrite, or audit concise product and engineering documentation using an independently expressed interpretation of the GitLab documentation style. Use for product guides, configuration, administration, tutorials, troubleshooting, contributor docs, and technical pages that must be searchable, precise, and localization-friendly.
- ▌ Mdn Web Docs · neeeophytee bundleDraft, rewrite, or audit web-platform documentation using an independently expressed interpretation of MDN Web Docs writing guidance. Use for HTML, CSS, JavaScript, Web API references, browser-facing concepts, tutorials, learning material, compatibility notes, and examples for web developers at a stated experience level.
- ▌ Red Hat Docs · neeeophytee bundleDraft, rewrite, or audit modular enterprise technical documentation using an independently expressed interpretation of the Red Hat supplementary style guide. Use for administration, installation, configuration, security, troubleshooting, procedures, concepts, and references that must be precise, reusable, and supportable across product versions.
- ▌ Kubernetes Docs · neeeophytee bundleDraft, rewrite, or audit Kubernetes and cloud-native documentation using an independently expressed interpretation of Kubernetes documentation style. Use for concepts, tasks, tutorials, references, configuration, operations, and version-sensitive guidance involving clusters, workloads, APIs, kubectl, or Kubernetes resources.
- ▌ Mailchimp Content · neeeophytee bundleDraft, rewrite, or audit friendly customer and product communication using an independently expressed reference-only interpretation of Mailchimp's content guidance. Use for customer education, product copy, campaign guidance, onboarding, help messages, newsletters, and brand content that should be plainspoken, empathetic, and lightly playful only when the situation permits.
- ▌ Sec Plain English · neeeophytee bundleDraft, rewrite, or audit investor-facing financial and legal disclosure using an independently expressed interpretation of official SEC plain-English guidance. Use for prospectus summaries, risk factors, shareholder letters, offering materials, and securities disclosures that must be easier to understand without losing any material fact, qualification, condition, or uncertainty.
- ▌ Nhs Health Content · neeeophytee bundleDraft, rewrite, or audit patient-facing health and service content using an independently expressed reference-only interpretation of official NHS content guidance. Use for symptoms and conditions pages, appointment messages, treatment explanations, health-service instructions, and digital health journeys that must remain clinically accurate, inclusive, accessible, and explicit about next steps.
- ▌ Google Developer Docs · neeeophytee bundleDraft, rewrite, or audit developer documentation using an independently expressed interpretation of the Google developer documentation style. Use for API guides, tutorials, concepts, setup instructions, code explanations, command-line documentation, and technical content for a global developer audience.
- ▌ W3c Technical Reports · neeeophytee bundleDraft, restructure, or audit specification-style technical reports using an independently expressed reference-only interpretation of W3C editorial guidance. Use for protocols, standards, interoperability documents, conformance requirements, and technical specifications that must separate normative requirements from explanation and define precise, testable behavior without inventing requirements.
- ▌ Nasa Technical Writing · neeeophytee bundleDraft, restructure, or audit evidence-led scientific and engineering reports using an independently expressed reference-only interpretation of official NASA technical-publication guidance. Use for test and experiment reports, design descriptions, technical memoranda, engineering analyses, and scientific publications that must preserve measurements, conditions, limitations, and traceability from evidence to conclusions.
- ▌ Apple Interface Writing · neeeophytee bundleDraft, rewrite, or audit concise interface text using an independently expressed reference-only interpretation of Apple's Human Interface Guidelines for writing. Use for buttons, labels, settings, alerts, errors, onboarding, notifications, permissions, empty states, and multi-screen app flows where wording must make actions and consequences clear in limited space.
- ▌ Cdc Clear Communication · neeeophytee bundleDraft, rewrite, or audit evidence-based public-health communication using an independently expressed interpretation of the CDC Clear Communication Index. Use for patient explanations, health campaigns, risk and emergency messages, public-safety notices, and educational health material that must make one message and the audience's next action unmistakable.
- ▌ Microsoft Writing Style · neeeophytee bundleDraft, rewrite, or audit friendly, concise product and technical UX content using an independently expressed reference-only interpretation of Microsoft writing guidance. Use for product help, setup, support, interface text, error messages, and technical content that should feel conversational, scannable, global, and action-oriented.
- ▌ Agent Registry · neeeophytee bundleDiscover, register, and hire ERC-8004 autonomous agents across 22,000+ agents on EVM + Solana. Search by capability, check on-chain reputation scores, compare agent services by category with composite scoring, browse the service catalog, enrich agent profiles, check buyer reputation, and get complete machine-readable hiring instructions. Pay with USDC via x402.