Productivity

open-legal-products Skill

When Einstieg und Routing in Insolvency and Restructuring Law is required: clarifies role, objective, deadline, documents, and the appropriate next specialist workflow; produces a deadline and risk indicator with immediate action steps.

open-legal-products Skill

When Kaltstart Triage in Insolvency and Restructuring Law is required: clarifies role, objective, deadline, documents, and the appropriate next specialist workflow; produces a deadline and risk indicator with immediate action steps.

open-legal-products Bundle

Use this workflow to review uploaded documents and extract structured information into the tabular review columns defined in table-columns.yaml.

open-legal-products Bundle

Use this workflow to review contracts governed by Polish law and extract structured information into the tabular review columns defined in table-columns.yaml. Column prompts are in Polish, tuned to Polish contract practice and due diligence.

open-legal-products Bundle

Use this workflow to review Polish residential lease agreements (umowa najmu lokalu mieszkalnego) under the Civil Code (Kodeks cywilny, Art. 659 et seq.) and the Tenant Protection Act (ustawa z dnia 21 czerwca 2001 r. o ochronie praw lokatorów) and extract structured information into the tabular review columns defined in table-columns.yaml.

open-legal-products Bundle

Use this workflow to review Finnish residential lease agreements under the Act on Residential Leases (laki asuinhuoneiston vuokrauksesta 481/1995) and extract structured information into the tabular review columns defined in table-columns.yaml.

open-legal-products Bundle

Use this workflow to review Polish employment contracts (umowa o pracę) under the Labour Code (Kodeks pracy, Act of 26 June 1974) and extract structured information into the tabular review columns defined in table-columns.yaml.

open-legal-products Bundle

Use this workflow to review Finnish employment contracts under the Employment Contracts Act (työsopimuslaki 55/2001) and extract structured information into the tabular review columns defined in table-columns.yaml.

kesslernity Bundle

Turns process notes, a walkthrough or interview transcript, a transcript of a meeting recording or a stale existing procedure into a draft standard operating procedure: purpose and trigger, scope, definitions, roles with a RACI table, numbered steps with the check that closes each one, records produced, controls as stated, and open questions for the process owner. Every step traces to the source or reads UNKNOWN. Use when the user asks to "write an SOP from these notes", "turn this walkthrough into a procedure", "document how we do this", "draft the standard operating procedure for", "build a RACI for this process" or "tidy up this old procedure". Do not use for technical runbooks with commands and rollback, use runbook-drafter instead; for meeting minutes and action lists, use transcript-to-actions. Drafts for human review; never approves, authorises or signs off.

newkayak12 Skill

Use when preparing a service for production, hardening a flaky system, or building lasting operational improvements after an incident. Triggers on: "production readiness review", "going to prod", "pre-launch ops check", "system hardening", "운영 준비".

newkayak12 Skill

Use when starting a new feature or system from scratch and wanting to follow a full quality engineering process — from architecture through to incident readiness. Triggers on: "dev quality process", "새 기능 처음부터 제대로", "개발 품질 전체", "full dev cycle".

newkayak12 Skill

Use when you need to think through a complex problem systematically — generating ideas, stress-testing them, and converging on a decision. Triggers on: "think workflow", "깊이 있게 생각해보자", "아이디어를 체계적으로 검토", "structured thinking", "체계적 사고 프로세스".

newkayak12 Bundle

Use when executing an implementation plan with independent tasks using fresh subagents per task. Triggers on: "계획 실행해줘", "서브에이전트로 구현해줘", "subagent-driven", "plan 실행", "태스크별로 에이전트 배포해줘", "두 단계 리뷰로 구현", "현재 세션에서 계획 실행".

newkayak12 Skill

Use when preparing for a job application or career transition end-to-end — from analyzing a JD through to interview preparation. Triggers on: "job application workflow", "이직 준비 전체", "취업 프로세스 시작", "career transition", "job search process".

newkayak12 Skill

Use when stress-testing a high-stakes decision, strategic plan, or argument end-to-end. Triggers on: "critical thinking full process", "decision stress-test", "전략 검토 전체", "논리 전체 점검", "high-stakes decision review", "결정 제대로 검토해줘".

sboghossian-mini-claude-for-legal Skill

Use when a litigator needs a structured starting template for a court motion, adapted to the specific court, jurisdiction, and procedural rules. Covers motions to dismiss, summary judgment, compel, in limine, and sanctions, each adapted per jurisdiction (US, UK, DIFC, ADGM, UAE, KSA, LB, EG). Produces jurisdiction-appropriate structure, required legal standards, and a checklist of required components before filing.

sboghossian-mini-claude-for-legal Skill

Transactional — Privacy Impact Assessment (PIA / DPIA)

charlieviettq Skill

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop. Use when a visually important website task should generate design images, analyze them, then implement code.

charlieviettq Skill

Require fresh verification evidence before claiming tests pass, builds succeed, or work is complete. Use when finishing a task, creating a PR, or reporting status. Triggers: "done", "fixed", "passes", "ready to merge", "all tests green".

charlieviettq Skill

Lightweight design smell review for modules and APIs—coupling, cohesion, naming, boundaries, and unnecessary complexity. Use before large refactors or when code feels hard to change. Complements gstack/review (diff-focused). Triggers: "design review", "code smell", "too complex", "refactor structure".

charlieviettq Skill

Systematically triage failing tests by grouping errors, fixing root causes in priority order, and verifying incrementally. Use when CI fails, test suite is broken, or multiple tests fail after a refactor or merge. Triggers: "tests failing", "fix tests", "CI red", "make tests pass".

charlieviettq Skill

Four-phase root-cause debugging—reproduce, compare patterns, hypothesize, fix with tests. Use when errors are unclear, fixes failed twice, or symptoms keep returning. Triggers: "root cause", "debug systematically", "why is this broken", "still failing".

charlieviettq Skill

Triage and address GitHub PR review comments systematically—classify, respond, fix or defer with rationale. Use when a PR has review feedback, requested changes, or unresolved threads. Triggers: "PR comments", "review feedback", "address comments", "requested changes".

charlieviettq Skill

Receive code review feedback constructively—verify claims, prioritize fixes, push back with evidence when needed. Use when acting on reviewer comments or preparing a second review round. Triggers: "code review", "reviewer said", "address review", "feedback on PR".

charlieviettq Skill

Ask the minimum clarifying questions before implementing when scope, constraints, or success criteria are unclear. Use when a request has multiple plausible interpretations, missing acceptance criteria, or ambiguous environment constraints. Triggers: "unclear", "ambiguous", "not sure what you want", "multiple options".

charlieviettq Skill

Request a focused code review with scope, diff context, and severity-ordered findings. Use before merge or between plan tasks when quality gate is needed. Triggers: "request review", "review my diff", "pre-merge review", "second pair of eyes".

charlieviettq Skill

Apply test-first discipline for behavior changes and bugfixes: define expected behavior, add or run a failing test, then implement minimally. Use when fixing bugs, changing logic, or adding features that need regression protection. Triggers: "bugfix", "TDD", "regression test", "behavior change", "add test".

charlieviettq Bundle

Write a structured spec before significant implementation—objective, commands, boundaries, testing, and success criteria. Use when starting a feature, project, or multi-file change without a written spec.

charlieviettq Skill

Plan deprecation and migration—replacement first, consumer migration, strangler and adapter patterns, zombie code removal. Use when sunsetting APIs, libraries, or legacy modules. Triggers: "deprecate", "migration plan", "sunset", "remove legacy", "strangler".

charlieviettq Skill

Implement multi-file changes in thin vertical slices—implement, test, verify, commit. Use when a feature touches more than one file or feels too large for one pass. Triggers: "incremental", "vertical slice", "one step at a time", "small commits".

charlieviettq Skill

Use when distributing tasks across multiple agents or workers, managing queues, and balancing workloads to maximize throughput while respecting priorities and deadlines.

charlieviettq Skill

Decompose specs into small, ordered tasks with acceptance criteria and verification steps. Use when you have requirements and need an implementable plan or task list. Triggers: "break down tasks", "implementation plan", "task breakdown", "plan mode".

charlieviettq Skill

Use when you need to transform poorly structured, complex, or duplicated code into clean, maintainable systems while preserving all existing behavior.

kesslernity Bundle

Turns one meeting transcript or recap into a DRAFT action-items document (decisions, owned and dated action items with verbatim source quotes, open questions), a task list ready for the user to enter into their task tracker, and one DRAFT follow-up email per action owner, all returned in the chat for the user to store, create or send. Use when the user shares, names or points to a meeting transcript or recap and asks to "pull the action items from this transcript", "who owns what after today's call", "draft follow-up emails to each owner" or "turn this recap into tasks". Do not use for full minutes, use meeting-minutes-writer instead; a brief before a meeting is meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Turns one decision discussion (meeting transcript, chat thread, email chain or notes) into a DRAFT one-page decision memo: the decision as stated, status, options considered, evidence cited, dissent recorded verbatim, owner, effective date and review date, with UNKNOWN for anything the discussion did not settle. Use when the user asks to "write up the decision", "record what we decided", "capture the decision from this thread", "draft the decision memo" or "add this to the decision log". Do not use for full minutes or action items, use transcript-to-actions instead; for a technical design decision, use architecture-decision-record; for a paper seeking a decision not yet taken, use board-paper-skeleton. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Applies a change-safety review to any requested file, mail or calendar change: lists every create, modify, move, rename, archive or delete before proposing it, marks destructive items as requiring the user's typed confirmation, proposes versioned file names instead of overwrites, declines to draft bulk destructive operations, and drafts a change journal entry for the user to keep. Use when the user asks to "clean up this folder", "delete the old versions", "reorganise these files", "archive everything older than a year", "rename and move these documents" or "make sure nothing gets overwritten while we work", or when any task is about to create or modify files, emails or calendar items. Do not use for backing up, journalling or restoring a skills folder, use skills-backup-keeper instead. Drafts for human review; never approves, authorises or signs off.