Business & Operations
Operations, strategy, finance, sales, support, management, and planning
Browse business & operations skills
Showing 2,329–2,352 of 32,371 skills
The GM operating-rhythm skill for a small company run from Google Docs/Sheets. Reads the source-of-record chain in precedence order (strategy alignment section → H2 project tracker (status SOR) → the ops team's weekly log → OKR & KPI tracker → per-function progress sheets), derives per-item state (ends-soon · overdue · undated · propose-done · direction-unlabelled), and produces a fixed-shape WEEKLY GM BRIEF: runway line first, the ≤3 things only the GM can unblock, two clocks, P0/P1 status b...
Team-side weekly heartbeat on the COMPANY Planning Main Tracker (SOR tab of the H1 / H2 / YE cycle) — zynkr-gm's record-side companion. Reads the `<cycle> 專案項目` tab, derives per-item state with zynkr-gm's rules VERBATIM (ENDS_SOON · OVERDUE · UNDATED · STALLED · PROPOSE_DONE · DIRECTION_UNLABELLED — its scripts when installed, else the copied rules) and prints the zh-TW Team Weekly agenda block in one fixed six-section shape (cadence → OVERDUE/ENDS_SOON → UNDATED/掛 All → 各 owner P0/P1 + Δ → P...
Build or extend Zynkr's planning Main Tracker (the cycle's system of record) from a NORMALIZED item list — the planning-session-synth handoff or a pasted table. Fresh cycle: copy the template tracker (never edit it) → 「<year> <cycle> Planning Main Tracker」 → cycle-named tabs → fill the SOR tab with L1 header rows + N.NN numbering, 重要×緊急 → Priority formula, the 專案項目小記 pivot, 狀態 colours. Existing tracker: fill the empty SOR tab session-synth left, append rows under the right L1 block, or add a ...
Propagate a FINALIZED planning Main Tracker into Zynkr's satellite planning suite after an H1 / H2 / YE planning session: for the integrated plan Doc and every per-LOB plan Doc it composes and inserts a dated top-of-body Refresh addendum (thesis sharpened · what changed vs the previous plan · open decisions · the P0 list with owners · management fixes from the retro), and for the OKR & KPI Tracker it rebases the OKRs (Objective = 策略主軸, KR = P0 items with Owner + Tracker #) and mirrors P0+P1 I...
Same-day digestion of a Zynkr planning offsite (H1 / H2 / year-end): turn the session transcript + whiteboard photos into the Main Tracker's working tabs — verbatim 「② 白板原文」 (pen colour + 判讀信心 高/中/低), the MECE re-cut 「③ 去重與歸類決策」 + 「④ MECE 檢查」 with every merge/split/move ruling written down, the 「<cycle> 回顧總結」 retro table with 5 重點結論, the README tab, a normalized item list handed to planning-tracker-builder, and the recap mail as a Gmail DRAFT (never sent). Trigger on /planning-session-synth o...
Build the BEFORE-THE-ROOM pack for a Zynkr planning session (H1 / H2 / YE): copy the session-workbook template Sheet and re-fill its five tabs for the new cycle (Read Me · Agenda 8 blocks · Pre-work by LOB 8 rows · Laundry List + Eisenhower seeds · Eisenhower Matrix) from the Main Tracker, the OKR tracker, the per-LOB plan Docs and the 1:1 Docs; write per-owner one-pager text blocks into a 「Pre-work — <cycle>」 Doc; hand a 16-slide template-fill request to /zynkr-slide (or print the slide text...
Audit ONE line of business (an L1 LOB such as 3.0 Operations) after a planning cycle: inventory its Drive folder, read its plan Doc + Refresh addendum and its rows in the planning Main Tracker, and cross-check five gap classes — P0/P1 items with no doctrine/SOP or owner-named plan, role docs / SOPs that contradict the plan (stale tools, stale owners), docs the plan cites that do not exist, superseded snapshots without a [SUPERSEDED] banner, and open decisions the plan needs from the founder. ...
The "looking back in numbers" scoreboard for a Zynkr planning cycle (H1 / H2 / YE). Seeds KPIs from the session workbook's Pre-work by LOB tab + the OKR tracker's KRs, routes each to ONE readable source (Main Tracker 完成 counts · planning-tracker-sync's `tracker-snapshots` tab · OKR status · Calendar event counts by title pattern · Gmail Fireflies recap counts · numbers the user pastes; zynkr-gm's kpi-map.md when installed), writes a `Scoreboard` tab (KPI · source · <cycle>-start · <cycle>-end...
Turn ONE teammate's shared 1:1 Doc (weekly WB entries), their LOB plan Doc and the tracker rows they own into a zh-TW 「年度計畫_<name>」 Google Doc in the planning hub folder — six fixed sections (過去一年成果總覽 · 策略透鏡 C1–C4 · 復盤 放大/收割/停止或改造 · 年度計劃 3–5 主軸 · OKR · 接下來) with every claim tagged to its WB date, plus a 12-line slide summary block for that person's session one-pager. Trigger on /planning-1on1-annual-digest or when Peter says "幫 <name> 整理年度計畫", "從 1:1 文件整理 <name> 的年度回顧", "把 <name> 的 1:1 筆記變成年度...
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
Commission a project to the Programme SDLC bundle. Tailored entry point with Programme-specific audience guidance; equivalent to /sdlc-core:commission --option programme.
Commission a project to the Programme SDLC bundle. Tailored entry point with Programme-specific audience guidance; equivalent to /sdlc-core:commission --option programme.
Stage source files into library/raw/, converting non-markdown formats via markitdown (PDF/DOCX/PPTX/XLSX/HTML/CSV) or pandoc (TeX/EPUB/RST/ORG). Adds provenance frontmatter. No agent dispatch.
Expert guide for pushing metadata, lineage, and query logs to Monte Carlo from any data warehouse.
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
Estimate calcium-normalized Gapon selectivity coefficients from paired exchange and solution chemistry, or initialize depth-explicit EcoSIM Gapon inputs from the closest bundled ecosystem template when paired chemistry is unavailable. Use when deriving or checking EcoSIM GKC4, GKCH, GKCA, GKCM, GKCN, or GKCK values; matching a target ecosystem, climate, vegetation, and management regime to a starting profile; remapping template values to target soil layers; or documenting that template-based ...
Map observed site vegetation, species lists, land-cover descriptions, or plant management PFTs to EcoSIM vegetation codes using templates/ecosim_pftpar_20260303.nc.cdl. Use when choosing or validating EcoSIM pft_type values, pfts entries, pfts_short categories, pfts_long plant type meanings, or the combined short-code plus Koppen climate numerical code used by plant management inputs.
Prepare, validate, inspect, and edit EcoSIM soil management inputs using soil_mgmt_in NetCDF, editable Excel workbooks, and optional JSON files. Use when checking fertilizer, tillage, or irrigation management data; converting soil-mngt NetCDF to Excel for editing; converting edited Excel back to JSON or NetCDF; decoding fertf/tillf/irrigf selector variables; or validating EcoSIM ReadManagementMod.F90 soil-management inputs.
Extract one EcoSIM PFT parameter record from a PFT-parameter NetCDF file into a standalone NetCDF. Use when Codex needs to isolate all parameters for a given EcoSIM six-character PFT code such as ndlf34, or a four-character pfts_short value plus Koppen climate code, while preserving all non-PFT-specific variables such as pfts_short, pfts_long, and Koppen metadata.
Extract and update the EcoSIM output-variable catalog from Fortran history-field registration calls such as hist_addfld1d and hist_addfld2d. Use only when explicitly asked to update, regenerate, refresh, or rebuild the list of EcoSIM output variables from HistDataType.F90 or related F90 source; do not invoke for ordinary EcoSIM output analysis unless the variable list itself must be updated.
Prepare, validate, and edit EcoSIM plant management inputs using pft_mgmt_in NetCDF, editable Excel workbooks, and optional PlantMgmtWriter.py JSON files. Use when creating or checking natural PFT management data, converting pft-mngt NetCDF to an Excel sheet for editing, converting edited Excel back to JSON or NetCDF, validating pft_type/pft_pltinfo/pft_mgmt entries, or preparing PlantMgmtWriter.py inputs for EcoSIM.
Extract typical annual GPP, annual evapotranspiration, mid-season LAI, mid-season root biomass, mid-season shoot biomass, median canopy height, maximum primary-root depth, Vcmax at 25oC, and Jmax at 25oC from EcoSIM h0 NetCDF output files. Use when asked to derive these EcoSIM output targets from a selected .ecosim.h0.*.nc file for model-output processing, trait checks, or benchmark summaries.
Extract point-scale CMIP6 historical and SSP future climate data from the Pangeo Google Cloud catalog and convert them into bias-corrected additive or multiplicative anomalies for LSM or EcoSIM climate forcing. Use when a task needs site latitude/longitude, scenario-specific CMIP6 variables, vapor pressure derived from huss and ps, calendar-aware day-of-year climatologies, or projected change summaries for the 2050s and 2090s.
Extract dominant-component soil profile variables for EcoSIM grid or template inputs from gSSURGO, with FAO HWSD v2.0 fallback when gSSURGO data are unavailable or incomplete. Use when deriving soil depth, bulk density, field capacity, wilting point, hydraulic conductivity, texture, rock fraction, pH, CEC, or soil organic carbon; or when converting EcoSIM grid NetCDF files to editable Excel workbooks and back.