Loading...
Loading...
Found 358 Skills
Prepare, submit, and optimize Chrome Web Store listings. Covers workflow, checklist, rejection reasons, listing optimization, and CI/CD automation.
Expert ISO 27001 compliance assistant for security and compliance teams. Use this skill whenever a user asks about ISO 27001 or ISO/IEC 27001, including any of the following: gap analysis, auditing, compliance assessments, control checklists, policy writing, document generation, Statement of Applicability (SoA), risk assessment, risk registers, risk treatment plans, Annex A controls, ISMS implementation, clause requirements, certification readiness, transitioning from 2013 to 2022, control implementation guidance, incident response policies, access control policies, supplier security, or any information security management system (ISMS) topic. Trigger even if the user doesn't say "skill" — any ISO 27001 or ISMS question should use this skill.
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.
Systematic pre-publication manuscript audit producing a structured refactoring report with section-level diagnostics, citation hygiene analysis, and submission-readiness assessment. Use this skill whenever the user uploads a manuscript, paper, thesis chapter, journal submission, or conference paper and asks for review, feedback, editing, refactoring, pre-submission check, proofreading, or quality audit. Also trigger when the user says "review my paper", "check before submission", "is this ready to submit", "pre-pub checklist", "manuscript review", "refactor my paper", or asks about citation consistency, argument coherence, or formatting compliance. Covers partial requests like "check my references" or "does the abstract work" — the full diagnostic surfaces issues across all facets even when only one was asked about.
Critical analysis of research papers, academic manuscripts, preprints, and technical studies — evaluating methodology, claims-evidence alignment, contribution significance, and intellectual honesty. Produces coherent analytical responses (not checklists) that distinguish genuine weaknesses from standard field limitations. Governs intellectual posture: collegial reader, not adversarial reviewer. Triggers on: "critique this paper", "review this research", "what do you think of this paper", "analyze this study", "evaluate the methodology", "is this paper sound", "assess this research", "strengths and weaknesses of this paper", "does the evidence support the claims". Use this skill when the user provides a research paper, preprint, or technical study and asks for critical evaluation of its scientific merit, methodology, or contribution — not formatting, citation hygiene, or submission readiness (use manuscript-review for those).
Follow this sub-process for code optimization — handle tasks where 'behavior remains unchanged but structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step by step according to the method library, and obtain manual approval for each step'. Trigger scenarios: When the user mentions phrases like 'optimize / refactor / rewrite / split / poor performance / too long code' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).
Ultra-lightweight channel for refactor processes - used when changes are obviously too small to justify the full scan → design → apply three-stage workflow. AI directly identifies 1-3 low-risk optimization points, confirms with the user once, modifies in-place using classic methods, and validates itself by running tests. No scan checklist, no design documentation, no multi-step HUMAN verification required. Trigger scenarios: When the user says "quick refactor", "small refactor", "simply optimize XX function", "modify directly", "skip all those steps", and the scope of changes is clearly limited to a single function/single component, with tests available for self-validation.
Enter this sub-process when conducting code optimization — handle tasks where 'behavior remains unchanged, structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step-by-step according to the method library, and require manual approval for each step'. Trigger scenarios: Users mention phrases like 'optimize it / refactor / rewrite / split it / poor performance / code is too long' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).
Use this for {{FRAMEWORK}} components, pages, hooks, forms, and frontend refactors that should follow Panapps coding standards and review checklist.
Use when writing, generating, or drafting a pull request description. Always use this skill when the user asks to "write a PR description", "create a PR", "draft a pull request", "generate PR text", or similar. Produces a complete, structured PR description following the team's conventions: ticket-key title, Purpose, Approach with implementation details, and a Pre-Review Checklist.
Designing lead magnets that earn the email. The discipline of building gated content (ebooks, templates, checklists, swipe files, mini-courses, free tools) that delivers genuine standalone value while qualifying the lead and warming them for what comes next. Honest about thin-bait (overpromises, underdelivers), kitchen-sink-resource (everything, helps with nothing), and earned-value-magnet (delivers standalone value while qualifying the lead). Triggers on lead magnet, gated content, opt-in offer, ebook, checklist, template, swipe file, mini-course, free tool, content upgrade, freebie, opt-in, list-building offer. Also triggers when an audience is being asked for an email and the offer attached to that ask needs design discipline, when previous lead magnets converted but did not produce qualified leads, or when a lead magnet is being scoped for the first time.
This skill should be used when the user asks to draft or structure STR reports, suspicious transaction reports, SAR, suspicious activity reports, draft STR, STR narrative, file suspicious activity, AML STR, goAML, FinCEN SAR, suspicion narrative, or MLRO report. Guides jurisdiction-agnostic STR/SAR drafting—narrative structure (who, what, when, where, why suspicious), red flags and typologies, transaction aggregation and chronology, subject identification fields, supporting documentation checklists, quality review before filing, and escalation to MLRO/compliance—not TM rule building (aml-compliance), full LE case management, legal filing duty determination (commercial-counsel), or deep blockchain tracing (blockint skills). Complements aml-compliance, aml-cft, auditor, compliance-engineer, and commercial-counsel.