Activity Maps

Map key activities and their relationships. Use for operational analysis and capability development.

Security Scan

This is an instruction-only skill that provides templates and guidance for mapping activities and relationships; its declared requirements and runtime instructions are consistent and do not request credentials, binaries, or installs.

Purpose & Capability

Name and description (activity/system mapping) match the SKILL.md content; there are no unexpected dependencies, environment variables, or binaries requested.

Instruction Scope

Instructions are limited to generating activity maps, templates, analysis, and recommendations. They do not reference system files, environment variables, external endpoints, or broad data collection steps.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk or downloaded at install time.

Credentials

The skill requires no environment variables, credentials, or config paths; requested capabilities are proportionate to the task of producing activity maps.

Persistence & Privilege

always is false and there are no privileged behaviors. The skill can be invoked autonomously by the agent (platform default), which is reasonable for this type of guidance-only skill.

Assessment

This skill is instruction-only and appears coherent and low-risk. Before installing, consider: (1) it will process whatever input you give it—avoid sending sensitive secrets or private data into prompts; (2) test it with non-sensitive examples to validate output quality; and (3) if you prefer tighter control, disable autonomous invocation at the agent level so the skill runs only when you explicitly call it. No network downloads, credentials, or system access are requested by the skill itself.

Metadata

• Name: activity-maps
• Description: Activity system mapping and analysis
• Triggers: activity map, activity system, value chain, operations

Instructions

Map and analyze activity systems for $ARGUMENTS.

Framework

Activity System Map

              ┌──────────────┐
              │   Activity A │
              │   (Core)     │
              └──────┬───────┘
                     │
        ┌────────────┼────────────┐
        │            │            │
   ┌────▼────┐  ┌────▼────┐  ┌────▼────┐
   │Activity B│  │Activity C│  │Activity D│
   │(Support)│  │(Support) │  │(Support) │
   └────┬────┘  └────┬────┘  └────┬────┘
        │            │            │
   ┌────▼────┐  ┌────▼────┐  ┌────▼────┐
   │Activity E│  │Activity F│  │Activity G│
   └─────────┘  └─────────┘  └─────────┘

Activity Categories

Category	Description	Examples
Core	Differentiating	R&D, design
Critical	Must excel	Quality, delivery
Supporting	Enable core	HR, finance
Outsourceable	Non-critical	Cleaning, admin

Output

## Activity Map: [Business/Function]

### Core Activities

| Activity | Description | Capability Level |
|----------|-------------|------------------|
| [Activity 1] | [Desc] | Strong |
| [Activity 2] | [Desc] | Medium |

### Supporting Activities

| Activity | Supports | Performance |
|----------|----------|-------------|
| [Activity 3] | [Core activity] | Good |
| [Activity 4] | [Core activity] | Needs improvement |

### Activity Relationships

| From | To | Type | Strength |
|------|-----|------|----------|
| A | B | Enables | Strong |
| B | C | Feeds | Medium |
| C | D | Supports | Weak |

### Gap Analysis

| Activity | Required | Current | Gap |
|----------|----------|---------|-----|
| [Activity] | [Level] | [Level] | [Gap] |

### Recommendations

1. **[Core Activity]**: [Investment/focus area]
2. **[Gap]**: [Action to close]
3. **[Relationship]**: [Strengthening action]

Tips

• Start with core differentiating activities
• Map relationships and dependencies
• Identify bottlenecks
• Focus on strategic activities