skill-bibtex-tool
A Python CLI tool
What this skill does
<!-- ⚠️ AGENT INSTRUCTIONS: This is a skeleton SKILL.md template When details about this CLI tool become clearer, update this file with: 1. **When to use section**: Add 3-5 specific use cases (bullet points) 2. **Purpose section**: Expand the tool's purpose and capabilities 3. **When to Use This Skill**: Add specific scenarios and anti-patterns 4. **Installation**: Keep the standard installation instructions 5. **Quick Start**: Add 2-3 practical quick start examples 6. **Core Commands**: Add detailed documentation for each CLI command in collapsible sections 7. **Advanced Features**: Document advanced features like verbosity, shell completion, pipelines 8. **Troubleshooting**: Add common issues and solutions 9. **Best Practices**: Add 3-5 best practices for using the tool 10. **Resources**: Update with actual GitHub URL and documentation links CRITICAL REQUIREMENTS: - Keep description in frontmatter ≤ 50 characters (hard limit) - Use progressive disclosure with <details> tags - Include comprehensive examples in each section - Provide troubleshooting guidance - Keep always-visible content minimal (overview only) - Put detailed info in expandable sections - Use emojis for section summaries (📖 Core, ⚙️ Advanced, 🔧 Troubleshooting) --> # When to use <!-- TODO: Add specific use cases when CLI functionality is known --> - When you need to use bibtex-tool CLI tool - When you need comprehensive guidance on CLI commands - When you need examples and troubleshooting # bibtex-tool Skill ## Purpose <!-- TODO: Expand with specific tool capabilities --> This skill provides access to the `bibtex-tool` CLI tool. A Python CLI tool. ## When to Use This Skill **Use this skill when:** <!-- TODO: Add specific scenarios, e.g., --> - You need to understand how to use bibtex-tool - You need comprehensive examples and patterns - You need troubleshooting guidance **Do NOT use this skill for:** <!-- TODO: Add anti-patterns, e.g., --> - Tasks unrelated to bibtex-tool - Quick syntax lookups (use slash commands instead) ## CLI Tool: bibtex-tool <!-- TODO: Add tool overview --> The `bibtex-tool` is a command-line interface tool that A Python CLI tool. ### Installation ```bash # Clone and install git clone https://github.com/dnvriend/bibtex-tool.git cd bibtex-tool uv tool install . ``` ### Prerequisites - Python 3.14+ - [uv](https://github.com/astral-sh/uv) package manager ### Quick Start <!-- TODO: Add 2-3 practical quick start examples when commands are known --> ```bash # Example 1: Basic usage bibtex-tool --help # Example 2: Show version bibtex-tool --version ``` ## Progressive Disclosure <details> <summary><strong>📖 Core Commands (Click to expand)</strong></summary> <!-- TODO: Add detailed command documentation for each CLI command --> <!-- Template for each command: ### command-name - Brief Description Detailed explanation of what this command does. **Usage:** ```bash bibtex-tool command-name ARGUMENT [OPTIONS] ``` **Arguments:** - `ARGUMENT`: Description of argument - `--option VALUE` / `-o VALUE`: Description of option - `-v/-vv/-vvv`: Verbosity (INFO/DEBUG/TRACE) **Examples:** ```bash # Example 1: Basic usage bibtex-tool command-name "example" # Example 2: With options bibtex-tool command-name "example" --option value # Example 3: Pipeline usage bibtex-tool command-name "example" --json | jq '.' ``` **Output:** Description of what this command returns. --- Repeat for each command... --> ### help - Show Help Information Display help information for CLI commands. **Usage:** ```bash bibtex-tool --help bibtex-tool COMMAND --help ``` **Examples:** ```bash # General help bibtex-tool --help # Command help bibtex-tool command --help # Version info bibtex-tool --version ``` </details> <details> <summary><strong>⚙️ Advanced Features (Click to expand)</strong></summary> <!-- TODO: Add advanced features documentation --> ### Multi-Level Verbosity Logging Control logging detail with progressive verbosity levels. All logs output to stderr. **Logging Levels:** | Flag | Level | Output | Use Case | |------|-------|--------|----------| | (none) | WARNING | Errors and warnings only | Production, quiet mode | | `-v` | INFO | + High-level operations | Normal debugging | | `-vv` | DEBUG | + Detailed info, full tracebacks | Development, troubleshooting | | `-vvv` | TRACE | + Library internals | Deep debugging | **Examples:** ```bash # INFO level - see operations bibtex-tool command -v # DEBUG level - see detailed info bibtex-tool command -vv # TRACE level - see all internals bibtex-tool command -vvv ``` --- ### Shell Completion Native shell completion for bash, zsh, and fish. **Installation:** ```bash # Bash (add to ~/.bashrc) eval "$(bibtex-tool completion bash)" # Zsh (add to ~/.zshrc) eval "$(bibtex-tool completion zsh)" # Fish (save to completions) bibtex-tool completion fish > ~/.config/fish/completions/bibtex-tool.fish ``` --- ### Pipeline Composition <!-- TODO: Add pipeline examples when commands support --json and --stdin --> Compose commands with Unix pipes for powerful workflows. **Examples:** ```bash # Example pipeline workflows will be added when CLI commands are implemented bibtex-tool command --json | jq '.' ``` </details> <details> <summary><strong>🔧 Troubleshooting (Click to expand)</strong></summary> ### Common Issues **Issue: Command not found** ```bash # Verify installation bibtex-tool --version # Reinstall if needed cd bibtex-tool uv tool install . --reinstall ``` <!-- TODO: Add command-specific troubleshooting when functionality is known --> **Issue: General errors** - Try with verbose flag: `-vv` to see detailed error information - Check that all prerequisites are installed - Ensure you're using Python 3.14+ ### Getting Help ```bash # Show help bibtex-tool --help # Command-specific help bibtex-tool COMMAND --help ``` </details> ## Exit Codes - `0`: Success - `1`: Client error (invalid arguments, validation failed) - `2`: Server error (API error, network issue) - `3`: Network error (connection failed, timeout) ## Output Formats <!-- TODO: Update with actual output formats when commands are implemented --> **Default Output:** - Human-readable formatted output - Varies by command **JSON Output (`--json` flag):** - Machine-readable structured data - Perfect for pipelines and processing - Available on commands that support structured output ## Best Practices <!-- TODO: Add command-specific best practices --> 1. **Use verbosity progressively**: Start with `-v`, increase to `-vv`/`-vvv` only if needed 2. **Check help first**: Use `--help` to understand command options 3. **Leverage shell completion**: Install completion for better CLI experience ## Resources - **GitHub**: https://github.com/dnvriend/bibtex-tool - **Python Package Index**: https://pypi.org/project/bibtex-tool/ - **Documentation**: <!-- TODO: Add documentation URL if available -->
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.