Mine-FNL

@mine-fnl source repo

15 skills
0 followers
7 hours ago last updated

▌
Csp Headers · mine-fnl
Use when designing or hardening a Content-Security-Policy header for an HTTP application. Applies when the user asks for "CSP", "Content Security Policy", "nonce-based CSP", "strict-dynamic", or "XSS hardening headers". Do not use for non-web platforms (native, mobile), for CORS configuration (use a CORS skill), or for setting CSP via a managed WAF without owning the header value.

0 installs
▌
Wireguard Vpn · mine-fnl
Use when setting up a WireGuard VPN on a Linux server or client, when troubleshooting a WireGuard handshake, or when migrating from an OpenVPN / IPSec deployment. Applies when the user asks for "WireGuard setup", "wireguard endpoint", "wg-quick", or "kernel VPN tunnel". Do not use for IPSec tunnels, for managed SaaS VPN products (Tailscale, Cloudflare Tunnel), or for non-Linux platforms.

0 installs
▌
API Pagination · mine-fnl
Use when designing or implementing pagination for a REST or HTTP API. Applies when the user asks for "page numbers", "cursor pagination", "infinite scroll", "load more", or "next/prev links". Do not use for GraphQL pagination (use a GraphQL-specific skill), batch exports, or single-shot endpoints that fit under the response size limit.

0 installs
▌
Git Bisect Bugs · mine-fnl
Use when a regression has been introduced in a long-lived codebase and the user knows the bug is present in `HEAD` but absent in some older release. Applies when the user asks for "find the bad commit", "git bisect", "binary search the history", or "which commit introduced this bug". Do not use for bug hunts that do not have a known-good commit (use `git log -S` or a manual review), or for bisecting test runtime rather than correctness.

0 installs
▌
Refactor Rename · mine-fnl
Use when renaming a class, function, type, file, module, or public symbol across a codebase. Applies when the user asks for "rename this symbol", "rename a file safely", or "refactor the API name". Do not use for adding a new symbol (use the language's author flow), or for renaming a database column or a public URL — those have their own migration playbooks.

0 installs
▌
Skillmd Authoring · mine-fnl
Use when authoring, reviewing, or refactoring a SKILL.md file that follows the open SKILL.md spec at agentskills.io. Applies when the user asks for "write a skill", "review my SKILL.md", or "what should go in the frontmatter". Do not use for authoring plain Markdown documentation, for writing prompt templates, or for designing product features — SKILL.md is one specific file format with strict rules.

0 installs
▌
Incident Postmortem · mine-fnl
Use when an incident has been resolved and the team needs to write up what happened, why, and what changes. Triggers: "write the postmortem", "incident review", "what happened during the outage", "let's schedule the postmortem". Do not use during an active incident (use an incident-response skill instead), for near-miss reviews that did not cause user impact, or for security-incident write-ups (those have different disclosure requirements).

0 installs
▌
Postgres Migrations · mine-fnl
Use when authoring or reviewing a PostgreSQL schema migration that runs against a live production database. Applies when the user asks for "add a column", "add an index", "backfill", "ALTER TABLE safely", or "zero-downtime migration". Do not use for application-level ORM migrations on a dev database, for greenfield schemas with no traffic, or for non-PostgreSQL databases (MySQL, SQLite).

0 installs
▌
Code Review Checklist · mine-fnl
Use when reviewing a pull request, merge request, or diff for any nontrivial change. Applies when the user asks for "review this PR", "checklist for code review", or "what to look at when reviewing". Do not use for reviewing marketing copy, design mockups, or non-code artifacts; use a domain-appropriate review skill instead.

0 installs
▌
Python Package Release · mine-fnl
Use when releasing a new version of a Python package — bumping version, cutting a tag, publishing to PyPI, writing the changelog, or announcing the release. Triggers: "cut a release", "publish to PyPI", "bump version", "this is ready to ship", "tag and release". Do not use for first-time repo setup, for the inner loop of writing code, or for releasing non-Python artifacts.

0 installs
▌
SQL Query Optimization · mine-fnl
Use when a SQL query is slow, when EXPLAIN ANALYZE output is confusing, or when designing a query that will run against a non-trivial dataset (millions of rows, multi-tenant table, partitioned data). Triggers: "why is this slow", "this query times out", "optimize this query", "the report takes 20 minutes". Do not use for query syntax errors (use the database's error message), schema design questions (use a dedicated schema skill), or NoSQL / document-store queries.

0 installs
▌
Typescript Strict Mode · mine-fnl
Use when migrating a JavaScript codebase to TypeScript with strict mode, or when tightening `tsconfig.json` after a migration has plateaued. Applies when the user asks for "enable strict", "noImplicitAny", "strict null checks", or "fix the type errors". Do not use for adding TypeScript to a brand-new project with no existing JS (start with `tsc --init` and a permissive config), and not for non-TypeScript typed languages.

0 installs
▌
API Error Response Format · mine-fnl
Use when designing or implementing an HTTP API's error response shape, when reviewing a PR that adds a new error path, or when a client SDK needs to consume errors. Triggers: "how should we return errors", "what's the JSON error schema", "this 500 leaked a stack trace", "the error structure is inconsistent". Do not use for logging-format questions, exception handling inside the service, or for non-HTTP protocols (gRPC, message queues).

0 installs
▌
Debug Distributed Systems · mine-fnl
Use when an incident spans more than one service, when a request fails inconsistently, or when the user asks for "trace the request", "find the slow hop", or "correlate the logs". Applies when the system under investigation uses trace IDs, OpenTelemetry, or any cross-service correlation header. Do not use for single-process bugs (use a language-specific debugger), or for client-side rendering issues.

0 installs
▌
Security Review Checklist · mine-fnl
Use when reviewing a code change for security implications — pull requests touching auth, secrets, crypto, input handling, deserialization, network calls, file system access, or any user-controlled data flow. Triggered by "security review", "is this safe to ship", "any vulns here", or "audit this change". Do not use for general code review (use code-review-checklist), threat modelling new systems (use a dedicated threat-modelling skill), or compliance audits.

0 installs

15 published skills