All authors

Claude Skills by Jamie-BitFlight
github.com/Jamie-BitFlight284 skills0 installs362 views
- CiteUse when the primary outcome is creating publishable source-attributed content from URLs or supplied material, including research summaries, articles, briefs, and posts whose factual claims and quotations need reader-visible, verifiable citations.Votes: 0GitHub stars: 67
- Doc To SkillUse when the primary outcome is creating a new portable Agent Skill directory from one local documentation file, documentation directory, or Git repository, including mixed text and capability-gated binary sources that require exhaustive source-to-output accounting.Votes: 0GitHub stars: 67
- OptimizeUse when the primary outcome is refining an existing AI-facing artifact without dropping behavior, including SKILL.md, AGENTS.md, CLAUDE.md, rules, prompts, and agent definitions that need sharper invocation, structure, or completion criteria.Votes: 0GitHub stars: 67
- The Rewrite RoomUse when the user explicitly asks Rewrite Room to route documentation work, or when audit/sync/freshness, user-facing authoring, citation-driven writing, docs-to-skill conversion, and AI-instruction optimization overlap and exactly one workflow must be chosen.Votes: 0GitHub stars: 67
- Twelve Factor AppReference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.Votes: 0GitHub stars: 67
- Verification GateEnforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.Votes: 0GitHub stars: 67
- Xdg Base DirectoryWhen an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing cross-platform file storage with platformdirs.Votes: 0GitHub stars: 67
- Ai Design Tools/install-skill nextlevelbuilder/ui-ux-pro-max-skill ``` ```bash npx uipro-cli install ``` The CLI detects the active AI assistant environment or accepts an explicit `--assistant` flag and generates the correct integration files (e.g., `.claude/CLAUDE.md` entry, Kiro workflow YAML, Copilot instructions file). Once installed, the skill auto-activates on natural language requests: ```text User: Build a SaaS dashboard landing page in Next.js with a modern glassmorphism style Claude: [queries desi...Votes: 0GitHub stars: 67
- Developer Tools**Research Date**: 2026-05-10 **Source URL**: <https://github.com/Jamie-BitFlight/claude_skills/blob/main/.claude/skills/gh/SKILL.md> **GitHub Repository**: <https://github.com/cli/cli> **Version at Research**: 2.87.2 (released 2026-02-20) **License**: MIT (GitHub CLI project) ---Votes: 0GitHub stars: 67
- Developer ToolsScrapling Skill is a Claude Code community skill that wraps the Scrapling Python library to provide intelligent web scraping and HTML data extraction capabilities. It implements an automated decision tree to select optimal Fetcher strategies (curl_cffi, Playwright, Camoufox, or pure parsing) based on target website characteristics, then generates and executes parameterized Python scripts for scraping. The skill supports static pages, Cloudflare-protected sites, form-based login sessions, JavaScrVotes: 0GitHub stars: 67
- Skill Generation ToolsCodebase Recon is a multi-agent compatible skill that analyzes git history to understand a codebase before reading any code. It reveals project health, risk areas, team structure, and development momentum through structured analysis of seven codebase dimensions. The skill is designed for developers onboarding to new projects, technical leads auditing codebases, and consultants evaluating code repositories.Votes: 0GitHub stars: 67
- Task Management**Resource**: Internal Communications Skill Module **Repository**: [ComposioHQ/awesome-codex-skills/internal-comms](https://github.com/ComposioHQ/awesome-codex-skills/tree/master/internal-comms) **License**: Apache License 2.0 **Latest Update**: 2026-05-07Votes: 0GitHub stars: 67
- Backend ResolutionHow to determine which backlog backend a project is configured to use, and what to do with the answer. Use when about to call a backend-specific tool, choosing between a GitHub-only and a Beads-native operation, or reporting which store a result came from.Votes: 0GitHub stars: 67
- Dh Cli UsageGives the dh CLI command and the directory of dh's scripts, both resolved from this skill's own directory. Use before running a dh plan, backlog, artifact or dispatch command, or a script from dh's scripts directory, and when an mcp__plugin_dh_* server failed to connect.Votes: 0GitHub stars: 67
- Root Cause Tracing ProcessTrace bugs, CI failures, and unexpected behavior from reproduced evidence to a causal mechanism and governing contract. Distinguish product, architecture, test-oracle, and harness defects; investigate intermittent failures with controlled experiments and report unresolved evidence explicitly.Votes: 0GitHub stars: 67
- Output Style CreatorCreate, validate, and diagnose Claude Code output styles — the file that sets Claude's role, tone, and response format for every turn. Use when asked to write, bundle, or force an output style for a plugin, to set keep-coding-instructions or force-for-plugin, when a style is not taking effect or the wrong one applies, or when choosing between an output style, CLAUDE.md, a skill, and an agent for a persistent behavior change.Votes: 0GitHub stars: 67
- Topic SpecialistResearch a specific technology, library, system, protocol, or tool to answer a concrete technical question with source-traceable evidence. Use when current implementation details, version behavior, configuration, compatibility, or authoritative technical facts must be verified rather than recalled. Also use when explicitly asked to incorporate verified findings into an existing skill.Votes: 0GitHub stars: 67
- Analyze Change ImpactAnalyze the causal system-wide impact of a proposed change across behavior, interfaces, state/data, runtime dependencies, tests, documentation, controls, people/processes, and model/prompt/context behavior. Use before planning when lexical reference search is insufficient to establish blast radius and verification obligations.Votes: 0GitHub stars: 67
- Audit Documentation DriftAudit documentation claims against implementation and authoritative repository evidence. Use when checking whether README, architecture, configuration, API, usage, or feature documentation is stale, incomplete, contradicted by code, missing implemented behavior, or inconsistent with a normative contract.Votes: 0GitHub stars: 67
- Evaluate Acceptance CriteriaExecute structured acceptance checks and record their observed results for later comparison. Use to capture a pre-change baseline or a post-change verification state without treating expected nonzero baseline results as execution failure.Votes: 0GitHub stars: 67
- Review Accessibility ChangeReview changed user-interface or CLI presentation behavior for accessibility failures. Use for an independent accessibility perspective on a defined change set.Votes: 0GitHub stars: 67
- Review Performance ChangeReview a change for material performance regressions or unbounded resource behavior. Use for an independent performance perspective on a defined change set.Votes: 0GitHub stars: 67
- Review Quality ChangeReview a code change for correctness-maintainability defects not owned by a narrower security/performance/accessibility perspective. Use for an independent quality perspective on a defined change set.Votes: 0GitHub stars: 67
- Review Security ChangeReview a change for security defects such as secret exposure, injection, authentication/authorization failures, unsafe deserialization, and dependency risk. Use for an independent security perspective on a defined change set.Votes: 0GitHub stars: 67
- Synchronize DocumentationSynchronize existing documentation with an observed code/configuration/API change while preserving each document's purpose and authority. Use after implementation changes can make documentation stale, incomplete, or internally inconsistent.Votes: 0GitHub stars: 67
- Synthesize Review FindingsSynthesize multiple independent structured review verdicts into one lossless deduplicated punch list. Use when findings from several review perspectives must be merged without inventing, dropping, or changing source verdicts.Votes: 0GitHub stars: 67
- Test DesignerSeparate required change validation from permanent test retention, then design maintenance-adjusted contract tests before writing them, including each TDD increment. Use when planning acceptance or regression evidence, selecting system/integration/unit boundaries and oracles, or deciding what evidence a software change needs. Produces a direct validation plan plus a risk-proportionate retained-test plan or explicit no-new-test decision, not production code or a passing-test claim.Votes: 0GitHub stars: 67
- Test ReviewerReview existing tests against the software and contracts they actually exercise. Use to assess whether a test has justified unique protection, detects consequential faults, tolerates valid refactors, earns its lifecycle cost, or deserves strengthening, replacement, consolidation, or removal consideration. Reviews are read-only and evidence-backed, including TDD and regression tests.Votes: 0GitHub stars: 67
- Validate Implementation PlanValidate whether an implementation plan can achieve its stated outcome before execution. Use to check requirement coverage, task contracts, dependencies, data/artifact flow, testability, ownership, impact coverage, and executable ordering without checking whether implementation already exists.Votes: 0GitHub stars: 67
- Verify Factual ClaimVerify one falsifiable factual claim against evidence appropriate to the claim. Use when a concrete assertion about software, documentation, configuration, releases, or repository behavior must be classified as VERIFIED, REFUTED, or INCONCLUSIVE.Votes: 0GitHub stars: 67
- Verify Feature OutcomesVerify after implementation that a feature achieved its required user/system outcomes. Use for goal-backward post-implementation verification that tests observable behavior rather than merely checking code existence.Votes: 0GitHub stars: 67
- Verify Implementation ContractsCompare explicit design/specification contracts with the implementation in a defined change scope. Use to verify signatures, types, schemas, invariants, and other stated contracts without expanding into general code quality review.Votes: 0GitHub stars: 67
- Verify IntegrationVerify that changed components are actually connected into the intended end-to-end system flow. Use when checking imports/exports, registrations, data/control flow, configuration consumption, call paths, and boundary compatibility after implementation.Votes: 0GitHub stars: 67
- Python Quality AuditUse when the user asks for a read-only, actionable audit of Python code quality, modernization, maintenance burden, ecosystem opportunities, or Pythonic design across a PR, git diff, staged/unstaged changes, files, or directories.Votes: 0GitHub stars: 67