Feature Request
This skill should be used when the user asks to "file a feature", "request a feature", "log a feature request", "suggest an improvement", or mentions a marketplace plugin enhancement that should be tracked. Files feature requests as GitHub issues on cadrianmae/claude-marketplace.
What this skill does
# File a Feature Request
File a feature request as a GitHub issue on `cadrianmae/claude-marketplace`. This is for logging only — do NOT attempt to implement the feature in this session.
## Quick Example
```bash
/cadrianmae-issues:feature tts plugin - add volume control per-voice
```
## Workflow
1. Ask 1-2 clarifying questions if the description is unclear:
- What is the use case? When would this be used?
- What should the behaviour look like?
2. Determine which marketplace plugin is affected — infer from conversation context, the description, or ask the user
3. Compose the issue title and body using the template below
4. Create the issue with `gh issue create`
5. Confirm the issue URL and return to the user's current work
## Labels
- Always apply `enhancement`
- If a specific plugin is affected, also apply `plugin:<name>` (e.g. `plugin:cron`, `plugin:tts`)
## Issue Creation
After gathering details, compose the issue and file it:
```bash
gh issue create \
--repo cadrianmae/claude-marketplace \
--title "<concise feature title>" \
--body "<issue body>" \
--label enhancement \
--label "plugin:<name>"
```
### Issue Body Template
```markdown
## Description
<clarified description>
## Use Case
<from clarifying questions, or 'Not specified' if user skipped>
## Proposed Behaviour
<from clarifying questions, or 'Not specified' if user skipped>
---
Plugin: <plugin name or n/a>
Date: <YYYY-MM-DD>
```
## After Filing
Respond with the issue URL, e.g.:
"Feature request filed: https://github.com/cadrianmae/claude-marketplace/issues/43. Continuing with your current work."
Return focus to whatever the user was working on before this command.
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.