本文へ移動
cccskills
無料GitHub で公開

facilities-and-workplace

Runs the physical and hybrid workplace — space planning, leases, health and safety, office services, and the operational side of where people work. Use this to plan space, evaluate a lease or office move, set up a hybrid workplace, handle facilities incidents, or decide what office services are worth funding.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.7 KB
  • references/sources.md1.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Facilities and workplace

Facilities is invisible when it works and is the loudest topic in the company when it does not. It is also, after payroll, frequently the largest fixed commitment a business makes.

Occupational health and safety, accessibility, and building compliance are legally regulated and vary by jurisdiction — and in the United States by state as well as federally. This structures the decision and names what to ask; it is not a substitute for qualified advice or a licensed inspection.

Space follows how people actually work

Plan from observed attendance, not from headcount or from policy. A hybrid organization with a three-day expectation does not need desks for everyone, and does need more of the rooms people compete for — small meeting spaces and focus rooms, which are chronically undersupplied because they are easy to convert into desks.

Measure before committing: actual peak occupancy by day, room utilization, and what people leave the building to do. Most offices are simultaneously too large in aggregate and too small on Wednesday.

Leases are the commitment nobody models

A lease is a multi-year fixed obligation signed on a headcount forecast that will be wrong. Treat it as the capital decision it is — finance:capital-allocation for the appraisal, legal-risk:contract-review for the terms.

The terms that matter later: break clauses and what they cost, expansion and contraction rights, what "restore to original condition" obliges you to spend at exit, and who pays for what when the building fails. Dilapidations at lease end routinely surprise organizations that never read the clause.

Health, safety, and the duty of care

The obligation follows the worker, not the building. Home workers, field staff and contractors are in scope in most jurisdictions, which organizations discover late.

Keep the fundamentals current and evidenced: risk assessments, fire and evacuation, first aid, accident recording, and the statutory inspections the building requires. Evidence produced as a by-product of doing the work survives scrutiny; evidence assembled after an incident does not.

Physical access control sits with security:access-and-identity for policy; site incidents that disrupt operations escalate to operations:business-continuity-and-resilience.

Office services, and what is worth funding

Services are judged on whether they remove friction, not on generosity. Reliable connectivity, rooms that work on the first attempt, and somewhere to take a call beat perks that photograph well.

Absorbs the administrative-services function — mail, reception, supplies, workplace vendors — which sits here rather than as a separate department, alongside operations:vendor-management for the suppliers delivering it.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Size space from headcount rather than observed occupancy.
  • Sign a lease without modeling the exit and the dilapidations.
  • Treat health and safety as applying only to the office.
  • Fund visible perks while rooms and connectivity fail daily.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0362026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0362026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0362026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0362026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0362026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0362026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する