Computersystem- und IT-Manager

Führungsberufe · Berufliche Fähigkeiten & Kompetenzen · SOC 11-3021 · 3.002 Skills

Beruflicher Kontext

Diese O*NET-Aufgaben beschreiben den Beruf und geben Kontext für die SOC-Zuordnung. Sie bedeuten nicht, dass jeder aufgeführte Skill jede Aufgabe erfüllt.

Direct daily operations of department, analyzing workflow, establishing priorities, developing standards and setting deadlines.
Meet with department heads, managers, supervisors, vendors, and others, to solicit cooperation and resolve problems.
Review project plans to plan and coordinate project activity.

Die O*NET-Aufgaben werden in ihrer Ausgangssprache (Englisch) angezeigt. Die Aufgabendaten sind der O*NET® 29.1 Database der USDOL/ETA entnommen und werden gemäß CC BY 4.0 verwendet.

Repräsentative Quellen

Eine begrenzte Auswahl beliebter, diesem Beruf zugeordneter Skills, mit höchstens einem Skill je GitHub-Repository. Darunter folgt die vollständige Zuordnung.

davila7/claude-code-templates

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

alirezarezvani/claude-skills

/em:hard-call — Framework for decisions with no good options. Use when every option is painful and a structured 10/10/10 + regret-minimization pass is needed — e.g. choosing between a layoff and a down round, or killing a beloved product line.

hiclaw-find-worker

agentscope-ai/HiClaw

Use as a helper when the admin is assigning work but has not specified an existing Worker, so you need to search Nacos for a suitable Worker and ask whether to import it; also use when the admin explicitly says to import a Worker from the market or gives a direct nacos package URI.

intelligence-network-espionage

baojie/shiji-kb

Use when building covert informant networks to gather intelligence on rival states. Covers agent placement, secure communication channels, and intelligence verification for strategic advantage.

Alle zugeordneten Skills

Durchsuchen Sie die vollständige Zuordnung nach Repository-Beliebtheit oder jüngster Quellaktivität.

Namen und Beschreibungen der Skills bleiben in der vom Quell-Repository bereitgestellten Sprache.

Sortieren nach

davila7/claude-code-templates

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

alirezarezvani/claude-skills

/em:hard-call — Framework for decisions with no good options. Use when every option is painful and a structured 10/10/10 + regret-minimization pass is needed — e.g. choosing between a layoff and a down round, or killing a beloved product line.

alirezarezvani/claude-skills

/em:postmortem — Honest analysis of what went wrong. Use after a failed launch, missed quarter, or bad hire to run a blameless 5-Whys retrospective with a change register — e.g. dissecting why the Q3 release slipped six weeks.

alirezarezvani/claude-skills

Loads and manages company context for all C-suite advisor skills. Reads ~/.claude/company-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy/anonymization rules before external API calls. Use when starting any C-suite advisor session, when context looks stale or missing, or before sending company data to an external service.

alirezarezvani/claude-skills

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

hiclaw-find-worker

agentscope-ai/HiClaw

Use as a helper when the admin is assigning work but has not specified an existing Worker, so you need to search Nacos for a suitable Worker and ask whether to import it; also use when the admin explicitly says to import a Worker from the market or gives a direct nacos package URI.

intelligence-network-espionage

baojie/shiji-kb

Use when building covert informant networks to gather intelligence on rival states. Covers agent placement, secure communication channels, and intelligence verification for strategic advantage.

windsurf-license-management

jeremylongshore/claude-code-plugins-plus-skills

Manage Windsurf licenses and seat allocation. Activate when users mention "license management", "seat allocation", "billing optimization", "user licenses", or "subscription management". Handles license administration. Use when working with windsurf license management functionality. Trigger with phrases like "windsurf license management", "windsurf management", "windsurf".

windsurf-team-settings

jeremylongshore/claude-code-plugins-plus-skills

Manage team-wide Windsurf settings and AI policies. Activate when users mention "team settings", "organization config", "team policies", "shared settings", or "team standardization". Handles team configuration management. Use when working with windsurf team settings functionality. Trigger with phrases like "windsurf team settings", "windsurf settings", "windsurf".

high-output-management

wondelai/skills

Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation", "meeting overload", "new manager", "how do I run a 1:1", or "just got promoted to manager". Also trigger when structuring a manager's calendar and meeting cadence, designing team metrics, running planning, coaching delegation, or preparing performance reviews. Covers leverage, production principles, meetings as the medium of management, decisions, OKRs, and task-relevant maturity. For intrinsic motivation, see drive-motivation. For a company operating system, see traction-eos.

team-topologies

wondelai/skills

Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or "reorg". Also trigger when reorganizing engineering teams, aligning team and service boundaries, splitting a monolith and deciding ownership, reducing cross-team handoffs, or designing an internal platform. Covers the four team types, three interaction modes, the inverse Conway maneuver, and fracture planes. For bounded contexts, see domain-driven-design. For dependency direction in code, see clean-architecture.

new-manager-first-90-days

mohitagw15856/pm-claude-skills

Plan your first 90 days as a new manager — build trust, learn before changing, and avoid the classic first-time-manager mistakes. Use when asked to help me as a new manager, I just became a manager, first-time manager advice, or my first 90 days managing a team. Produces a phased 90-day plan (listen and learn, then set direction, then adjust), how to run your first 1:1s, the mindset shift from doer to enabler, common traps to avoid (doing it all yourself, changing too fast, avoiding hard conversations), and early wins that build credibility.