SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsopc-asset-ops

opc-asset-ops

Office & productivity

View repository

Updated 10-15 21:36

About this skill

Asset Accumulation

Goal

Help users determine "which outcomes are worth accumulating as assets," rather than building a complete system for the user all at once.

Core Principles

  • By default, read and write to opc-doc/
  • In teaching mode, first explain "asset accumulation" and "compounding"
  • By default, ask only one question at a time; if several questions are all very light and closely related to each other, they can be merged into 2 to 3
  • By default, give 3 priority accumulation directions, and attach 4. 我有自己的方案
  • Write the formal results only after the user confirms
  • Do not directly give recommended conclusions; only perform option analysis
  • At this stage, make asset priority judgments; do not directly produce asset content for the user

Boundaries of This Stage

What This Step Does

  • Identify which outcomes are worth accumulating as assets (judgment, not execution)
  • Clarify asset categories and the priority order for accumulation
  • Form an asset accumulation plan (planning layer)

What This Step Does Not Do

  • ❌ Do not directly write content for the user (such as copy, posts, template body text) — unless the user explicitly requests it
  • ❌ Do not create a complete content calendar schedule (categories can be planned, but each item is not expanded)

Note: The asset accumulation stage is the step in the entire methodology closest to execution. It is allowed to output specific template structure frameworks, but "filling in the content" is completed by the user themselves, or assistance is provided only after the user explicitly requests it.

What This Step Must Complete

  1. Identify accumulable outcomes
  2. Clarify asset categories
  3. Clarify priority accumulation directions
  4. Form the current asset accumulation plan

Priority Confirmation Order

  1. Which outcomes will be used repeatedly
  2. Which category of assets these outcomes belong to
  3. Which category to accumulate first at present
  4. How to organize this category of assets

Completion Criteria

  • 3 priority asset accumulation options have been formed
  • The user has confirmed the current priority accumulation direction

What This Step Needs to Explain

In teaching mode, first explain:

  • Asset accumulation is not note-taking; it is organizing the things that will still be used in the future
  • Assets can be content, methods, channels, data, or brand trust
  • The role of this step is to make the business increasingly less dependent on repeated ad hoc labor

Trigger Conditions

This skill is not the linear next step during the setup period, but a condition-triggered tool in the operations loop.

Trigger timing: during actual operations, the user discovers that certain actions are starting to repeat and wants to systematize them, so as not to start from scratch every time.

Common Trigger Signals:

  • "I've already written a lot of similar content, and I feel it can be organized into templates"
  • "I've used this process several times already, and it should be solidified"
  • "The questions clients ask are all pretty much the same, and I want to make a standard answer"

Prerequisite check: If the user has no actual operational output yet (has never done it at all), do not enter this skill; suggest going to execute first and then coming back.

Input

Read first:

  • opc-doc/outputs/06-mvp-design/*
  • opc-doc/outputs/07-conversion-loop/*
  • opc-doc/outputs/08-asset-ops/(historical accumulation records, whether there are additions this time)

If the above files are missing, determine whether the current conversation already contains a description of reusable outcomes.

  • If not, it means there are no outcomes that can be accumulated yet; suggest going to operate for a period of time first and then coming back

Execution Steps

  1. Explain the goal of this step
  2. By default, ask only one question at a time; if several questions are all lightweight and closely related, they can be combined into 2 to 3, for example:
    • What actions have you been repeating recently?
    • What kind of content or experience will you definitely use again in the future?
    • Would you rather first consolidate methods, content, or customer leads?
  3. After each round of answers, give brief feedback
  4. Generate 3 priority consolidation options, for example:
    • Method templates first
    • Content assets first
    • Channel and lead assets first
  5. Explain the applicable situations, advantages, and costs of each option
  6. By default, add 4. 我有自己的方案
  7. Let the user confirm, combine, modify, or directly propose their own version
  8. After the user confirms, then write the formal result

Output

The dialogue layer must include:

  1. Explanation of this step
  2. Summary of currently consolidatable results
  3. 3 priority options for asset consolidation + 4. 我有自己的方案
  4. The applicable situations, advantages, and costs of each option
  5. Ask the user to confirm or modify

Persistence checkpoint (must be completed after each trigger)

After the user clearly confirms the priority direction for asset consolidation,immediatelyuse the Write tool to write the file. Describing the conclusion in the dialogue does not count as persistence.

This skill supports multiple triggers. Each persistence uses a dated filename and does not overwrite historical records.

Write the file (use the current date, format YYYYMMDD):

  • opc-doc/outputs/08-asset-ops/asset-inventory-[YYYYMMDD].md(list of currently consolidatable results + asset category annotations)
  • opc-doc/outputs/08-asset-ops/action-plan-[YYYYMMDD].md(the priority consolidation direction confirmed this time and the next action)

Update the status file:

  • opc-doc/state/current-stage.json(write:{"stage": "08-asset-ops", "status": "completed", "next_stage": "execution", "summary": "一句话本次优先沉淀方向"}）
  • opc-doc/state/decisions.json(append this asset consolidation priority decision, noting the date)

After persistence is completed, inform the user in the dialogue:

"✅ This asset consolidation plan has been saved to opc-doc/. Go continue executing—when you encounter a bottleneck in operations, you can trigger a business review (opc-dashboard-review）。"

When to call other skills

  • After this skill is completed, it is not mandatory to proceed to other skills
  • If the user also reports an operational bottleneck, you can suggest triggering opc-dashboard-review
  • If this consolidation reveals a problem with the prior strategy, you can suggest returning to the corresponding foundation-building stage

Exception Handling

  • If the user does not yet have stable outputs, do not enter formal asset consolidation
  • If there are many outputs but they are scattered, classify them first and do not rush to build a complete system