scs-mcp 0.5.3__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,36 @@
1
+ # Python
2
+ __pycache__/
3
+ *.pyc
4
+ *.pyo
5
+ *.egg-info/
6
+ dist/
7
+ build/
8
+ .eggs/
9
+
10
+ # IDE
11
+ .vscode/
12
+ .idea/
13
+ *.swp
14
+
15
+ # Testing
16
+ .pytest_cache/
17
+ .coverage
18
+ htmlcov/
19
+
20
+ # Logs
21
+ *.log
22
+
23
+ # Archives
24
+ *.tgz
25
+ *.zip
26
+ *.tar.gz
27
+
28
+ # SCS runtime (generated data)
29
+ scs_registry/
30
+
31
+ # Local-only (not for GitHub)
32
+ docs/
33
+ tests/
34
+
35
+ # Claude
36
+ .claude/
scs_mcp-0.5.3/LICENSE ADDED
@@ -0,0 +1,190 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted by You to the Licensor for
132
+ inclusion in the Work shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ Copyright 2024-2026 SCS Team
179
+
180
+ Licensed under the Apache License, Version 2.0 (the "License");
181
+ you may not use this file except in compliance with the License.
182
+ You may obtain a copy of the License at
183
+
184
+ http://www.apache.org/licenses/LICENSE-2.0
185
+
186
+ Unless required by applicable law or agreed to in writing, software
187
+ distributed under the License is distributed on an "AS IS" BASIS,
188
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
189
+ See the License for the specific language governing permissions and
190
+ limitations under the License.
scs_mcp-0.5.3/PKG-INFO ADDED
@@ -0,0 +1,238 @@
1
+ Metadata-Version: 2.4
2
+ Name: scs-mcp
3
+ Version: 0.5.3
4
+ Summary: SCS - AI Capability Compiler. Turn scattered skills into verified, executable pipelines.
5
+ Project-URL: Homepage, https://github.com/lonyness/Skill-Compiler-System
6
+ Project-URL: Documentation, https://github.com/lonyness/Skill-Compiler-System#readme
7
+ Project-URL: Repository, https://github.com/lonyness/Skill-Compiler-System.git
8
+ Project-URL: Issues, https://github.com/lonyness/Skill-Compiler-System/issues
9
+ Project-URL: Changelog, https://github.com/lonyness/Skill-Compiler-System/releases
10
+ Author-email: SCS Team <scs-team@example.com>
11
+ License: Apache-2.0
12
+ License-File: LICENSE
13
+ Keywords: agent,ai,claude-code,cline,compiler,cursor,mcp,skills,windsurf
14
+ Classifier: Development Status :: 4 - Beta
15
+ Classifier: Intended Audience :: Developers
16
+ Classifier: License :: OSI Approved :: Apache Software License
17
+ Classifier: Programming Language :: Python :: 3
18
+ Classifier: Programming Language :: Python :: 3.9
19
+ Classifier: Programming Language :: Python :: 3.10
20
+ Classifier: Programming Language :: Python :: 3.11
21
+ Classifier: Programming Language :: Python :: 3.12
22
+ Classifier: Programming Language :: Python :: 3.13
23
+ Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
24
+ Classifier: Topic :: Software Development :: Compilers
25
+ Requires-Python: >=3.9
26
+ Requires-Dist: mcp>=1.0.0
27
+ Requires-Dist: pydantic>=2.0.0
28
+ Provides-Extra: dev
29
+ Requires-Dist: build>=1.0.0; extra == 'dev'
30
+ Requires-Dist: pytest>=7.0.0; extra == 'dev'
31
+ Requires-Dist: twine>=4.0.0; extra == 'dev'
32
+ Description-Content-Type: text/markdown
33
+
34
+ # SCS — Skill Compiler System
35
+
36
+ **[中文版](README_CN.md)**
37
+
38
+ > **Turn scattered skills into reliable workflows**
39
+
40
+ You've collected many skill files. But when it's time to actually use them:
41
+
42
+ - *"Which ones do I need for this task?"*
43
+ - *"Can they chain together? Or will it break halfway?"*
44
+ - *"Why do I have to manually piece them together, with no way to know if it will work?"*
45
+
46
+ **The core problem**: Skills are defined separately, but they need to work together. Nobody builds the bridges.
47
+
48
+ ---
49
+
50
+ ## What SCS Does for You
51
+
52
+ SCS is a **compiler**. It doesn't execute your skills — instead, it:
53
+
54
+ 1. **Scans all skills across all agents** — automatically discovers skills from Claude Code, Cursor, Windsurf, Cline, and 40+ platforms
55
+ 2. **Connects them** — automatically links skills that can work together
56
+ 3. **Verifies feasibility** — tells you if the workflow will run, where gaps exist
57
+ 4. **Generates a plan** — gives you a verified execution blueprint you can trust
58
+
59
+ Think of it like **Terraform Plan** for AI skills: you see a full preview with verification *before* anything runs.
60
+
61
+ ---
62
+
63
+ ## Cross-Platform Skill Discovery
64
+
65
+ When you call `scs_init()` without specifying a path, SCS automatically scans **all installed agent platforms**:
66
+
67
+ ```
68
+ scs_init()
69
+ → Scanning 4 platforms: claude_code, cursor, windsurf, cline
70
+ → Found 2465 skills, 176 artifact types
71
+ ```
72
+
73
+ **Important**: SCS discovers skills from all platforms, but each agent can only **invoke** skills in its own skills directory. If the recommended skill comes from another platform, you'll need to:
74
+ - Install that agent, or
75
+ - Copy the skill to your current agent's skills directory
76
+
77
+ The execution plan shows which platform each skill comes from, so you know what's available.
78
+
79
+ ---
80
+
81
+ ## One-Click Install
82
+
83
+ After cloning or downloading SCS, run one command:
84
+
85
+ ```bash
86
+ # Install to Claude Code
87
+ python -m scs.cli install --agent claude_code --force
88
+
89
+ # Or install to all supported agents
90
+ python -m scs.cli install --all --force
91
+ ```
92
+
93
+ Restart your agent and SCS tools are ready.
94
+
95
+ **What gets installed**:
96
+ 1. **MCP tools** — 8 SCS tools available in your agent
97
+ 2. **SCS Router Skill** — automatically injected to your agent's skills directory, guiding when to use SCS
98
+
99
+ **Supported agents**: Claude Code, Cursor, Windsurf, Cline
100
+
101
+ ---
102
+
103
+ ## Manual Install
104
+
105
+ If you prefer manual configuration, add to `~/.claude/settings.json`:
106
+
107
+ ```json
108
+ {
109
+ "mcpServers": {
110
+ "scs": {
111
+ "command": "python",
112
+ "args": ["-m", "scs.mcp_server"],
113
+ "cwd": "/path/to/SCS",
114
+ "env": { "PYTHONUTF8": "1" }
115
+ }
116
+ }
117
+ }
118
+ ```
119
+
120
+ Replace `/path/to/SCS` with your SCS directory.
121
+
122
+ ---
123
+
124
+ ## CLI Commands
125
+
126
+ | Command | What it does |
127
+ |---------|-------------|
128
+ | `scs install --agent claude_code` | Install to Claude Code |
129
+ | `scs install --all --force` | Install to all supported agents |
130
+ | `scs config` | Show configuration help |
131
+ | `scs path` | Show installation path |
132
+
133
+ ---
134
+
135
+ ## Tool Overview
136
+
137
+ After installation, your agent will have 8 new tools. You mainly use these 5:
138
+
139
+ ### scs_init — Initialize (call this first)
140
+
141
+ Scans skills, connects them, generates execution plans.
142
+
143
+ ```
144
+ # Scan all agents' skills
145
+ scs_init()
146
+
147
+ # Solve optimal path to a target
148
+ scs_init(target="ValidatedPRD", prefer="balanced")
149
+ ```
150
+
151
+ ### scs_scan — Scan (for large skill sets)
152
+
153
+ Scans and registers skills, but doesn't generate plans. Use when you have many skills.
154
+
155
+ ```
156
+ scs_scan()
157
+ → Scanned and registered 2465 skills
158
+ ```
159
+
160
+ ### scs_compile — Compile
161
+
162
+ Generates execution plans from already-scanned skills.
163
+
164
+ ```
165
+ scs_compile(target="ValidatedPRD")
166
+ → Compiled, found optimal path
167
+ ```
168
+
169
+ ### scs_list — List things
170
+
171
+ ```
172
+ scs_list(type="dag") # All execution plans
173
+ scs_list(type="skills") # All skills
174
+ scs_list(type="artifacts") # All artifact types
175
+ ```
176
+
177
+ ### scs_get — Get details
178
+
179
+ ```
180
+ scs_get(type="dag", id="plan_xxx")
181
+ scs_get(type="skill", id="prd_generator")
182
+ ```
183
+
184
+ ---
185
+
186
+ ## Typical Workflow
187
+
188
+ ```
189
+ # 1. Start fresh
190
+ scs_clear()
191
+
192
+ # 2. Scan and generate plans
193
+ scs_init()
194
+
195
+ # 3. See what was created
196
+ scs_list(type="dag")
197
+
198
+ # 4. Find optimal path to your target
199
+ scs_init(target="ValidatedPRD", prefer="balanced")
200
+
201
+ # 5. Understand why SCS chose this path
202
+ scs_diagnostics(plan_id="plan_xxx")
203
+ ```
204
+
205
+ ---
206
+
207
+ ## Large Skill Set Workflow
208
+
209
+ When you have 2000+ skills, use the phased approach to avoid timeout:
210
+
211
+ ```
212
+ scs_scan() # Step 1: Scan (~90s)
213
+ scs_list(type="artifacts") # Step 2: Explore
214
+ scs_compile(target="YourTarget") # Step 3: Compile (~30s)
215
+ ```
216
+
217
+ ---
218
+
219
+ ## Use Cases
220
+
221
+ SCS covers **8 industries, 176 artifact types**:
222
+
223
+ | Industry | Example artifacts |
224
+ |----------|------------------|
225
+ | Software | Requirements doc, source code, test report |
226
+ | Legal | Contract, legal opinion, due diligence report |
227
+ | Marketing | Marketing plan, brand guidelines, ad copy |
228
+ | Finance | Financial report, invoice, ROI analysis |
229
+ | HR | Job description, resume, performance review |
230
+ | Research | Research paper, literature review, grant application |
231
+ | Content | Article, blog post, video script |
232
+ | Operations | Service ticket, SOP, incident report |
233
+
234
+ ---
235
+
236
+ <p align="center">
237
+ <strong>SCS — Compile skills, not chaos.</strong>
238
+ </p>
@@ -0,0 +1,205 @@
1
+ # SCS — Skill Compiler System
2
+
3
+ **[中文版](README_CN.md)**
4
+
5
+ > **Turn scattered skills into reliable workflows**
6
+
7
+ You've collected many skill files. But when it's time to actually use them:
8
+
9
+ - *"Which ones do I need for this task?"*
10
+ - *"Can they chain together? Or will it break halfway?"*
11
+ - *"Why do I have to manually piece them together, with no way to know if it will work?"*
12
+
13
+ **The core problem**: Skills are defined separately, but they need to work together. Nobody builds the bridges.
14
+
15
+ ---
16
+
17
+ ## What SCS Does for You
18
+
19
+ SCS is a **compiler**. It doesn't execute your skills — instead, it:
20
+
21
+ 1. **Scans all skills across all agents** — automatically discovers skills from Claude Code, Cursor, Windsurf, Cline, and 40+ platforms
22
+ 2. **Connects them** — automatically links skills that can work together
23
+ 3. **Verifies feasibility** — tells you if the workflow will run, where gaps exist
24
+ 4. **Generates a plan** — gives you a verified execution blueprint you can trust
25
+
26
+ Think of it like **Terraform Plan** for AI skills: you see a full preview with verification *before* anything runs.
27
+
28
+ ---
29
+
30
+ ## Cross-Platform Skill Discovery
31
+
32
+ When you call `scs_init()` without specifying a path, SCS automatically scans **all installed agent platforms**:
33
+
34
+ ```
35
+ scs_init()
36
+ → Scanning 4 platforms: claude_code, cursor, windsurf, cline
37
+ → Found 2465 skills, 176 artifact types
38
+ ```
39
+
40
+ **Important**: SCS discovers skills from all platforms, but each agent can only **invoke** skills in its own skills directory. If the recommended skill comes from another platform, you'll need to:
41
+ - Install that agent, or
42
+ - Copy the skill to your current agent's skills directory
43
+
44
+ The execution plan shows which platform each skill comes from, so you know what's available.
45
+
46
+ ---
47
+
48
+ ## One-Click Install
49
+
50
+ After cloning or downloading SCS, run one command:
51
+
52
+ ```bash
53
+ # Install to Claude Code
54
+ python -m scs.cli install --agent claude_code --force
55
+
56
+ # Or install to all supported agents
57
+ python -m scs.cli install --all --force
58
+ ```
59
+
60
+ Restart your agent and SCS tools are ready.
61
+
62
+ **What gets installed**:
63
+ 1. **MCP tools** — 8 SCS tools available in your agent
64
+ 2. **SCS Router Skill** — automatically injected to your agent's skills directory, guiding when to use SCS
65
+
66
+ **Supported agents**: Claude Code, Cursor, Windsurf, Cline
67
+
68
+ ---
69
+
70
+ ## Manual Install
71
+
72
+ If you prefer manual configuration, add to `~/.claude/settings.json`:
73
+
74
+ ```json
75
+ {
76
+ "mcpServers": {
77
+ "scs": {
78
+ "command": "python",
79
+ "args": ["-m", "scs.mcp_server"],
80
+ "cwd": "/path/to/SCS",
81
+ "env": { "PYTHONUTF8": "1" }
82
+ }
83
+ }
84
+ }
85
+ ```
86
+
87
+ Replace `/path/to/SCS` with your SCS directory.
88
+
89
+ ---
90
+
91
+ ## CLI Commands
92
+
93
+ | Command | What it does |
94
+ |---------|-------------|
95
+ | `scs install --agent claude_code` | Install to Claude Code |
96
+ | `scs install --all --force` | Install to all supported agents |
97
+ | `scs config` | Show configuration help |
98
+ | `scs path` | Show installation path |
99
+
100
+ ---
101
+
102
+ ## Tool Overview
103
+
104
+ After installation, your agent will have 8 new tools. You mainly use these 5:
105
+
106
+ ### scs_init — Initialize (call this first)
107
+
108
+ Scans skills, connects them, generates execution plans.
109
+
110
+ ```
111
+ # Scan all agents' skills
112
+ scs_init()
113
+
114
+ # Solve optimal path to a target
115
+ scs_init(target="ValidatedPRD", prefer="balanced")
116
+ ```
117
+
118
+ ### scs_scan — Scan (for large skill sets)
119
+
120
+ Scans and registers skills, but doesn't generate plans. Use when you have many skills.
121
+
122
+ ```
123
+ scs_scan()
124
+ → Scanned and registered 2465 skills
125
+ ```
126
+
127
+ ### scs_compile — Compile
128
+
129
+ Generates execution plans from already-scanned skills.
130
+
131
+ ```
132
+ scs_compile(target="ValidatedPRD")
133
+ → Compiled, found optimal path
134
+ ```
135
+
136
+ ### scs_list — List things
137
+
138
+ ```
139
+ scs_list(type="dag") # All execution plans
140
+ scs_list(type="skills") # All skills
141
+ scs_list(type="artifacts") # All artifact types
142
+ ```
143
+
144
+ ### scs_get — Get details
145
+
146
+ ```
147
+ scs_get(type="dag", id="plan_xxx")
148
+ scs_get(type="skill", id="prd_generator")
149
+ ```
150
+
151
+ ---
152
+
153
+ ## Typical Workflow
154
+
155
+ ```
156
+ # 1. Start fresh
157
+ scs_clear()
158
+
159
+ # 2. Scan and generate plans
160
+ scs_init()
161
+
162
+ # 3. See what was created
163
+ scs_list(type="dag")
164
+
165
+ # 4. Find optimal path to your target
166
+ scs_init(target="ValidatedPRD", prefer="balanced")
167
+
168
+ # 5. Understand why SCS chose this path
169
+ scs_diagnostics(plan_id="plan_xxx")
170
+ ```
171
+
172
+ ---
173
+
174
+ ## Large Skill Set Workflow
175
+
176
+ When you have 2000+ skills, use the phased approach to avoid timeout:
177
+
178
+ ```
179
+ scs_scan() # Step 1: Scan (~90s)
180
+ scs_list(type="artifacts") # Step 2: Explore
181
+ scs_compile(target="YourTarget") # Step 3: Compile (~30s)
182
+ ```
183
+
184
+ ---
185
+
186
+ ## Use Cases
187
+
188
+ SCS covers **8 industries, 176 artifact types**:
189
+
190
+ | Industry | Example artifacts |
191
+ |----------|------------------|
192
+ | Software | Requirements doc, source code, test report |
193
+ | Legal | Contract, legal opinion, due diligence report |
194
+ | Marketing | Marketing plan, brand guidelines, ad copy |
195
+ | Finance | Financial report, invoice, ROI analysis |
196
+ | HR | Job description, resume, performance review |
197
+ | Research | Research paper, literature review, grant application |
198
+ | Content | Article, blog post, video script |
199
+ | Operations | Service ticket, SOP, incident report |
200
+
201
+ ---
202
+
203
+ <p align="center">
204
+ <strong>SCS — Compile skills, not chaos.</strong>
205
+ </p>