All authors
Claude Skills by monoes
github.com/monoes543 skills5 installs334 views
- ResearcherOrg role guidance for a researcher: investigate a codebase, technology or question and synthesize evidence-backed, cited recommendations for other roles. Covers broad-then-narrow search, cross-referencing sources, separating fact from inference, git history and flagging unknowns.Votes: 0GitHub stars: 21
- Resource AllocatorOrg role guidance for a resource allocator: forecast compute or agent capacity from workload patterns and allocate or scale ahead of demand. Covers p90 provisioning, confidence thresholds, gradual rollout, multi-objective trade-offs, bulkhead isolation and allocation KPIs.Votes: 0GitHub stars: 21
- Responsive DesignUse when implementing responsive CSS layouts: mobile-first breakpoints, container queries, fluid typography, Grid and Flexbox, and responsive images. Covers touch targets, logical properties and common overflow issues.Votes: 0GitHub stars: 21
- Returns Reverse LogisticsUse when running retail or e-commerce returns: RMA eligibility, condition grading, disposition routing, refunds, return fraud and warranty claims. Senior returns-manager persona with policy logic and recovery economics.Votes: 0GitHub stars: 21
- ReviewerOrg role guidance for a code reviewer: review code for correctness, security, performance and maintainability with specific, severity-ranked feedback. Short role checklist; the code-reviewer skill analyzes diffs in more depth.Votes: 0GitHub stars: 21
- RevopsUse when designing revenue operations: lead lifecycle stages, scoring and routing, marketing-to-sales handoff SLAs, CRM hygiene and funnel metrics. Covers PLG, sales-led and hybrid motions. For sales collateral use sales-enablement; for pricing use pricing-strategy.Votes: 0GitHub stars: 21
- Roadmap CommunicatorUse when preparing roadmap presentations, stakeholder updates, release notes, changelogs or feature announcements for executives, engineers or customers. Covers Now/Next/Later, timeline and theme-based formats plus audience-specific update patterns.Votes: 0GitHub stars: 21
- Rust EngineerUse when writing, reviewing or debugging Rust end to end: ownership and lifetimes, traits, thiserror error handling, async tokio, tests and clippy gates. Persona with reference files. For an idioms catalogue, use rust-patterns.Votes: 0GitHub stars: 21
- Rust PatternsUse when writing or reviewing Rust code and idiom is in question: ownership and borrowing, Result and ? error propagation, traits, concurrency and crate layout. A patterns catalogue with good vs bad examples; for an end-to-end build persona, use rust-engineer.Votes: 0GitHub stars: 21
- Safe ExecutorUse when an org role acts as safe executor and must run untrusted or agent-generated code without touching the host, other workloads or secrets. Covers microVM or gVisor isolation, hard resource limits, default-deny network, per-run filesystems, no shell interpolation and ephemeral sandboxes.Votes: 0GitHub stars: 21
- Sales CoachUse when an org role acts as sales coach and must improve rep performance through ongoing call reviews, skill-building and habit reinforcement. Covers weekly rubric-based review loops, one or two skills per session, GROW 1:1s, objection libraries and tracking behavior change. For discovery calls specifically, use discovery-coach.Votes: 0GitHub stars: 21
- Sales EnablementUse when creating B2B sales collateral reps will actually use: pitch decks, one-pagers, objection-handling docs, demo scripts and battlecards. Gathers value prop, sales motion and current assets first. For finding prospects use sales-prospecting; for running demos as a role use sales-engineer.Votes: 0GitHub stars: 21
- Sales EngineerUse when an org role acts as sales engineer and must run technical discovery, tailored demos and scoped POCs that prove the product fits the buyer. Covers discovery-to-demo mapping, POC scorecards, objection libraries and reference architectures. For making collateral, use sales-enablement.Votes: 0GitHub stars: 21
- Sales ProspectingUse when finding, qualifying and building a list of prospects to contact, for B2B SaaS, general B2B, local small businesses or first-customer demand signals. Branch-specific workflows from ICP definition to sourcing and qualification. For collateral, use sales-enablement.Votes: 0GitHub stars: 21
- Schema MarkupUse when adding, fixing or optimizing schema.org structured data with JSON-LD for rich results: FAQ, product, review, article, organization and more. Covers accuracy, Google's guidelines and validation.Votes: 0GitHub stars: 21
- Scientific BrainstormingUse when generating and prioritizing early-stage research ideas, with independent ideation, explicit assumptions, adversarial review and decision logs. Outputs are proposals, not findings. For judging existing evidence use scientific-critical-thinking.Votes: 0GitHub stars: 21
- Scientific Critical ThinkingUse when judging the rigor of scientific claims or studies: design validity, bias and confounding, statistics, and GRADE or Cochrane risk of bias. For rubric-scored feedback on a paper or proposal, use scientific-thinking-scholar-evaluation.Votes: 0GitHub stars: 21
- Scientific Thinking Literature ReviewUse when finding, screening, synthesizing and citing a body of academic papers or technical literature as a narrative, scoping or systematic review or meta-analysis. Covers question framing with PICO, search planning, screening, citation checks and evidence logs.Votes: 0GitHub stars: 21
- Scientific Thinking Scholar EvaluationUse when evaluating a paper, proposal, thesis chapter or review article with a repeatable 1-5 rubric on methods, evidence and citations. Supports comprehensive, targeted or comparative scope and revision feedback. For general claim appraisal, use scientific-critical-thinking.Votes: 0GitHub stars: 21
- Scientific VisualizationUse when creating or auditing publication-ready scientific figures in Matplotlib, Seaborn or Plotly: honest encodings, panels, uncertainty and color. Stresses data integrity, provenance and verifying live journal requirements.Votes: 0GitHub stars: 21
- Scientific WritingUse when drafting, revising or auditing scientific manuscripts or reports with evidence provenance, reporting guidelines and authorship accountability. Enforces no fabricated citations or results and confidentiality controls. For figures use scientific-visualization.Votes: 0GitHub stars: 21
- Scout ExplorerOrg role guidance for a scout explorer: map an unfamiliar codebase, dependency tree or system and report triaged, located findings without fixing anything. Covers scoping, breadth-first coverage, verified vs suspected findings, severity ordering and honest coverage reporting.Votes: 0GitHub stars: 21
- Secrets Vault ManagerUse when setting up secret management infrastructure: HashiCorp Vault, AWS Secrets Manager, Azure Key Vault or GCP Secret Manager, rotation and access audits. Covers Vault auth methods and policies, dynamic secrets, Kubernetes and CI/CD secret injection and leak revocation. Not for local env-file hygiene.Votes: 0GitHub stars: 21
- Secure Code GuardianUse when implementing security controls in code: auth and authorization, password hashing, parameterized SQL, input validation, CORS and CSP headers, JWTs. Workflow of threat model, implement, validate against OWASP Top 10 with checkpoints, plus TypeScript examples (bcrypt, Zod, Helmet). Implementation-focused, not an audit.Votes: 0GitHub stars: 21
- Security ArchitectUse when an org role acts as security architect and must design security in before build: threat models, trust boundaries, zero-trust and authn/authz patterns. Covers STRIDE, least privilege, defense in depth, secrets architecture, OIDC and mTLS, and ADRs for security controls.Votes: 0GitHub stars: 21
- Security AuditorUse when an org role acts as security auditor and must assess existing code and systems for exploitable vulnerabilities, rate severity, and re-test fixes. Covers OWASP and CWE checklists, auth and IDOR testing, SAST/SCA/secrets scanning and scoped audits. For smart contracts, use blockchain-auditor.Votes: 0GitHub stars: 21
- Security ReviewUse when adding auth, user input, file uploads, secrets, API endpoints or payment features: a pass/fail security checklist with TypeScript patterns. Covers secrets in env vars, Zod validation, SQL injection, XSS, CSRF, rate limiting and data exposure. A developer checklist; for full audits and pentest reports use security-reviewer.Votes: 0GitHub stars: 21
- Security ReviewerUse when conducting a security audit or pentest: SAST, dependency and secrets scans, manual auth and crypto review, and a severity-rated report. Tools include Semgrep, Bandit, Gitleaks, npm audit and Trivy, plus infrastructure and cloud checks; requires scoped authorization. For an in-flight coding checklist use security-review.Votes: 0GitHub stars: 21
- Senior Data ScientistUse when designing A/B tests, building statistical or predictive models, feature engineering pipelines or causal inference analyses in Python. Covers sample sizing, two-proportion z-tests, Bonferroni correction, feature pipelines with pandas and scikit-learn and model evaluation for production data science.Votes: 0GitHub stars: 21
- Senior DeveloperOrg role guidance for a senior developer: own full-stack feature delivery end to end with architecture-aware code, polished UI states and fast pages. Covers planning data flow first, matching stack idioms, accessibility, responsive testing, render-path performance and avoiding gold-plating.Votes: 0GitHub stars: 21
- Senior Pm PlaybookUse when managing an enterprise software project portfolio: health scoring, quantitative risk (EMV, Monte Carlo), capacity and RAG executive reports. Includes Python scripts for project health dashboards and risk matrices, WSJF/RICE prioritization and RACI governance. Project management, not product management; for product direction see senior-pm.Votes: 0GitHub stars: 21
- Senior PmUse when an org role acts as senior product manager and must set product direction and prioritize what gets built and why for a workstream. Covers problem-first framing, RICE/ICE/MoSCoW prioritization, success metrics before build, tight PRDs with out-of-scope sections and trade-off communication.Votes: 0GitHub stars: 21
- Seo AuditUse when auditing or diagnosing SEO issues on a site to produce prioritized findings on crawlability, indexation, technical, on-page and content quality. Includes a caveat that curl and web_fetch miss JS-injected schema markup. For implementing fixes use seo; for AI answer engines use ai-seo.Votes: 0GitHub stars: 21
- Seo SpecialistUse when an org role acts as SEO specialist and must grow organic visibility across search and AI answer engines through technical SEO, content and authority. Covers technical foundations, search intent, topical authority via internal linking, schema markup, Core Web Vitals and entity-first optimization.Votes: 0GitHub stars: 21
- SeoUse when implementing SEO fixes in a site's code: crawlability, canonicals, redirects, meta tags, structured data, Core Web Vitals and internal links. Engineering-oriented checklist with page-specific, implementable recommendations. For a diagnostic audit report use seo-audit; for pages at scale use programmatic-seo.Votes: 0GitHub stars: 21
- Shap Model ExplainabilityUse when explaining or auditing ML model predictions with SHAP in Python: choosing explainers and maskers, feature attributions and SHAP plots. Aligned to SHAP 0.52 and the shap.Explanation API; covers background data choice, multi-output models, additivity checks and local vs global visualizations.Votes: 0GitHub stars: 21
- Signup Flow CroUse when optimizing signup, registration, account creation or trial activation flows to raise completion rates. Covers field minimization, value before commitment, social auth, step design and friction audits. For post-signup activation use onboarding-cro; for marketing pages use page-cro.Votes: 0GitHub stars: 21
- Site ArchitectureUse when planning or restructuring a website's page hierarchy, navigation, URL structure or internal linking for SaaS, content, e-commerce or docs sites. Produces site maps, nav and URL patterns and redirect-aware restructures. Information architecture, not an SEO audit (see seo-audit) or copy (see copywriting).Votes: 0GitHub stars: 21
- Sms MarketingUse when planning or optimizing SMS or MMS marketing: welcome flows, abandoned cart texts, post-purchase, win-back, promotional or transactional sends. Covers when SMS beats email, A2P 10DLC and opt-in compliance, short code vs toll-free numbers and list economics.Votes: 0GitHub stars: 21
- Soc2 ComplianceUse when preparing a SaaS company for a SOC 2 Type I or Type II audit: Trust Service Criteria mapping, control matrices, gap analysis and evidence collection. Also covers readiness checklists, vendor management and continuous compliance. Framework playbook; for the auditor org role across SOC 2, ISO 27001 and HIPAA see compliance-auditor.Votes: 0GitHub stars: 21
- Social ContentUse when creating, scheduling or optimizing individual posts for LinkedIn, Twitter/X, Instagram, TikTok or Facebook, or triaging social engagement. Covers platform formats, hooks, repurposing and content calendars. For overall social strategy use social-media-manager.Votes: 0GitHub stars: 21
- Social Media ManagerUse when developing social media strategy: picking platforms, planning content calendars, auditing a weak presence or scaling community management. Three modes: build from scratch, audit and optimize, scale and systematize. For writing individual posts use social-content.Votes: 0GitHub stars: 21
- Social MediaUse when an org role acts as social media manager and must run a platform-native presence: per-platform content, posting cadence and fast community engagement. Covers audience-based platform choice, per-platform briefs and KPIs and conversation-driving content. Role guidance; for strategy playbooks see social-media-manager.Votes: 0GitHub stars: 21
- Solidity EngineerUse when an org role acts as Solidity engineer and must ship gas-efficient, audit-ready EVM contracts: tokens, upgradeable proxies and DeFi on L1 and L2s. Covers checks-effects-interactions, reentrancy guards, OpenZeppelin bases, storage packing and custom errors.Votes: 0GitHub stars: 21
- Spark EngineerUse when writing or tuning Apache Spark jobs: PySpark DataFrame and Spark SQL transformations, RDD pipelines, partitioning, shuffle and executor memory tuning. Also covers skew handling, caching and broadcast joins, Parquet I/O and Structured Streaming for big data ETL.Votes: 0GitHub stars: 21
- Spec Driven WorkflowUse when writing a spec before code: RFC 2119 requirements, Given/When/Then acceptance criteria, edge cases, API contracts and data models. Enforces no code without an approved spec and derives tests from acceptance criteria. For lighter intent clarification alongside work, see intent-driven-development.Votes: 0GitHub stars: 21
- Springboot PatternsUse when building or reviewing a Java Spring Boot backend: REST controllers, layered services, Spring Data JPA, validation, caching and async work. A catalogue of idioms with code; for end-to-end enterprise Java builds and microservices see java-architect.Votes: 0GitHub stars: 21
- Sprint PrioritizerUse when an org role acts as sprint prioritizer and must decide what enters the next sprint from a groomed backlog by value, effort, risk and dependencies. Covers RICE scoring before planning, sprint goals, cross-functional estimates and capacity limits. For writing stories and backlog ownership see agile-product-owner.Votes: 0GitHub stars: 21
- Sql ProUse when a SQL query is slow or you need complex joins, CTEs, window functions or aggregations, or to design or migrate a schema. Covers EXPLAIN ANALYZE, indexing, normalization and dialect differences across PostgreSQL, MySQL and SQL Server.Votes: 0GitHub stars: 21
- Sre EngineerUse when producing SRE artifacts: SLI/SLO definitions, error budget policies, golden-signal alerts, incident runbooks, capacity models, chaos tests. Includes blameless postmortems and toil-reduction automation. For the org role persona see sre.Votes: 0GitHub stars: 21