github-issue-writer
Creates well-structured Github issues for the upkeep-io project following standardized templates and best practices. Activate when users need to create or format issues for Upkeep-Io repository.
What this skill does
# Github Issue Writer ## Instructions You are assisting with drafting a high-quality Github Issues following Upkeep-Io standardized format. ### Issue Structure Create Issue using the following structure: 1. **User Story Format** (for features/enhancements): ``` As a [user type/role] I want to [action/capability] So that [benefit/value] ``` 2. **Context Section**: - Provide background information and business justification - Explain how this fits into the larger product strategy - Include references to related work or dependencies - Clearly identify what's in and out of scope 3. **Success Criteria**: - Write specific, testable acceptance criteria as scenario blocks - Format as "Given/When/Then" statements - Group related criteria under descriptive headers - Each criterion should be independently verifiable 4. **Technical Requirements**: - Separate requirements by domain (Frontend, Backend, etc.) - Include implementation guidelines, patterns, and approaches - Specify security considerations - Reference design materials when available 5. **Definition of Done**: - Include a checklist of completion criteria - Cover testing requirements, documentation, and reviews ### Best Practices - **Be Specific**: Avoid vague language; use concrete, measurable terms - **Be Comprehensive**: Ensure all aspects of implementation are covered - **Be User-Focused**: Connect technical requirements to user value - **Be Realistic**: Break large tasks into manageable pieces - **Prioritize Security**: Always include relevant security considerations ### Process (MANDATORY ORDER) 1. Ask clarifying questions to gather necessary details 2. **RESEARCH GATE (blocking):** - Use `mcp__Ref__ref_search_documentation` for technical requirements - Use `mcp__firecrawl__firecrawl_search` for domain/compliance requirements - Document sources consulted in your response 3. Structure information into the template sections 4. Cite sources in issue body where relevant 5. Ensure all required fields are completed 6. Format the final ticket for readability with proper markdown **You cannot proceed to step 3 without completing step 2. Issues without research may contain outdated or incorrect requirements.**
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.