@agentskillkit/agent-skills 1.0.1 → 3.2.2

package/.agent/skills/sequential-thinking/references/examples.md

@@ -1,274 +0,0 @@
-# Sequential Thinking Examples
-
-## Example 1: Database Performance Problem
-
-**Context**: API endpoints timing out, need to diagnose and fix.
-
-```typescript
-// Thought 1
-{
-  thought: "API timeout reports indicate database bottleneck. Need to profile queries first.",
-  thoughtNumber: 1,
-  totalThoughts: 6,
-  nextThoughtNeeded: true
-}
-
-// Thought 2
-{
-  thought: "Query logs show user profile endpoint makes 50+ queries per request. Classic N+1 pattern.",
-  thoughtNumber: 2,
-  totalThoughts: 6,
-  nextThoughtNeeded: true
-}
-
-// Thought 3
-{
-  thought: "Need to implement eager loading for relationships. Checking ORM documentation for optimal approach.",
-  thoughtNumber: 3,
-  totalThoughts: 7, // Adjusted scope
-  nextThoughtNeeded: true
-}
-
-// Thought 4
-{
-  thought: "ORM supports `include` for eager loading. Will need to modify 3 endpoints: /profile, /dashboard, /settings.",
-  thoughtNumber: 4,
-  totalThoughts: 7,
-  nextThoughtNeeded: true
-}
-
-// Thought 5
-{
-  thought: "Implementation complete. Testing shows queries reduced from 52 to 4 per request. Response time: 2.1s → 180ms.",
-  thoughtNumber: 5,
-  totalThoughts: 6, // Fewer steps than expected
-  nextThoughtNeeded: true
-}
-
-// Thought 6
-{
-  thought: "Success. Solution: eager loading eliminated N+1 queries. Next: add query monitoring to catch similar issues early.",
-  thoughtNumber: 6,
-  totalThoughts: 6,
-  nextThoughtNeeded: false // Done
-}
-```
-
-## Example 2: Architecture Decision with Branching
-
-**Context**: Choosing between microservices and monolith for new project.
-
-```typescript
-// Thought 1
-{
-  thought: "Need to decide architecture. Key factors: team size (5 devs), timeline (3 months), expected scale (10k users initially).",
-  thoughtNumber: 1,
-  totalThoughts: 8,
-  nextThoughtNeeded: true
-}
-
-// Thought 2
-{
-  thought: "Two viable approaches: monolith for simplicity or microservices for scalability. Need to evaluate both.",
-  thoughtNumber: 2,
-  totalThoughts: 10,
-  nextThoughtNeeded: true
-}
-
-// Branch A: Monolith approach
-{
-  thought: "Monolith pros: faster development, simpler deployment, easier debugging. Cons: potential future refactor cost.",
-  thoughtNumber: 3,
-  totalThoughts: 6,
-  branchFromThought: 2,
-  branchId: "monolith",
-  nextThoughtNeeded: true
-}
-
-{
-  thought: "For 10k users, single server handles load easily. Deployment: single container, straightforward CI/CD.",
-  thoughtNumber: 4,
-  totalThoughts: 6,
-  branchId: "monolith",
-  nextThoughtNeeded: true
-}
-
-{
-  thought: "Dev velocity high—team can ship in 3 months. Future scaling: can extract services later if needed.",
-  thoughtNumber: 5,
-  totalThoughts: 6,
-  branchId: "monolith",
-  nextThoughtNeeded: true
-}
-
-// Branch B: Microservices approach
-{
-  thought: "Microservices pros: independent scaling, service isolation. Cons: complexity overhead, distributed systems challenges.",
-  thoughtNumber: 3,
-  totalThoughts: 7,
-  branchFromThought: 2,
-  branchId: "microservices",
-  nextThoughtNeeded: true
-}
-
-{
-  thought: "For 5-person team: significant overhead in service coordination, API contracts, infrastructure management.",
-  thoughtNumber: 4,
-  totalThoughts: 7,
-  branchId: "microservices",
-  nextThoughtNeeded: true
-}
-
-{
-  thought: "Timeline risk: 3 months insufficient for robust microservices implementation. Need distributed tracing, service mesh, etc.",
-  thoughtNumber: 5,
-  totalThoughts: 7,
-  branchId: "microservices",
-  nextThoughtNeeded: true
-}
-
-// Convergence
-{
-  thought: "Comparing branches: monolith clearly better fit. Small team, tight timeline, modest initial scale. Microservices overhead unjustified.",
-  thoughtNumber: 6,
-  totalThoughts: 7,
-  nextThoughtNeeded: true
-}
-
-{
-  thought: "Decision: monolith with modular design. Extract services later if specific components need independent scaling.",
-  thoughtNumber: 7,
-  totalThoughts: 7,
-  nextThoughtNeeded: false
-}
-```
-
-## Example 3: Debugging with Revision
-
-**Context**: Feature works in dev, fails in production.
-
-```typescript
-// Thought 1
-{
-  thought: "Payment processing works locally but fails in prod. Checking error logs.",
-  thoughtNumber: 1,
-  totalThoughts: 5,
-  nextThoughtNeeded: true
-}
-
-// Thought 2
-{
-  thought: "Logs show 'Connection refused' to payment API. Likely firewall or network config issue.",
-  thoughtNumber: 2,
-  totalThoughts: 5,
-  nextThoughtNeeded: true
-}
-
-// Thought 3
-{
-  thought: "Checked firewall rules—payment API port (443) is open. Must be something else.",
-  thoughtNumber: 3,
-  totalThoughts: 6,
-  nextThoughtNeeded: true
-}
-
-// Thought 4 - Revision
-{
-  thought: "Wait—reviewing logs more carefully. Error message includes 'certificate verify failed'. Not firewall, it's SSL/TLS issue.",
-  thoughtNumber: 4,
-  totalThoughts: 6,
-  isRevision: true,
-  revisesThought: 2,
-  nextThoughtNeeded: true
-}
-
-// Thought 5
-{
-  thought: "Prod environment missing intermediate CA certificates. Dev works because it uses self-signed cert with verification disabled.",
-  thoughtNumber: 5,
-  totalThoughts: 6,
-  nextThoughtNeeded: true
-}
-
-// Thought 6
-{
-  thought: "Installed CA bundle on prod server. Payment processing now works. Root cause: incomplete SSL cert chain.",
-  thoughtNumber: 6,
-  totalThoughts: 6,
-  nextThoughtNeeded: false
-}
-```
-
-## Example 4: Complex Feature Planning
-
-**Context**: Building real-time collaborative editing feature.
-
-```typescript
-// Thought 1
-{
-  thought: "Real-time collab editing requires: WebSocket connections, operational transformation or CRDT, conflict resolution, presence tracking.",
-  thoughtNumber: 1,
-  totalThoughts: 12,
-  nextThoughtNeeded: true
-}
-
-// Thought 2
-{
-  thought: "Core decision: OT vs CRDT. OT requires central server for transform logic, CRDT enables P2P. For our use case, CRDT better.",
-  thoughtNumber: 2,
-  totalThoughts: 12,
-  nextThoughtNeeded: true
-}
-
-// Thought 3
-{
-  thought: "Research CRDT libraries: Yjs (popular, mature), Automerge (good TypeScript support). Yjs has better performance benchmarks.",
-  thoughtNumber: 3,
-  totalThoughts: 14, // Scope expanding
-  nextThoughtNeeded: true
-}
-
-// Thought 4
-{
-  thought: "Architecture: Yjs + WebSocket provider + persistence layer. Client-side: Yjs doc syncs via WebSocket. Server: broadcast updates + store snapshots.",
-  thoughtNumber: 4,
-  totalThoughts: 14,
-  nextThoughtNeeded: true
-}
-
-// Thought 5
-{
-  thought: "Implementation phases: (1) Basic sync, (2) Presence/cursors, (3) Persistence, (4) Conflict UI. Estimate 4 weeks total.",
-  thoughtNumber: 5,
-  totalThoughts: 14,
-  nextThoughtNeeded: true
-}
-
-// ... continues through implementation details
-
-// Final thought
-{
-  thought: "Plan complete. MVP: Yjs + WebSocket + Redis persistence. 4-week timeline. Main risk: scaling WebSocket connections—mitigate with load balancer sticky sessions.",
-  thoughtNumber: 14,
-  totalThoughts: 14,
-  nextThoughtNeeded: false
-}
-```
-
-## Usage Patterns Summary
-
-| Scenario | Pattern | Key Features |
-|----------|---------|--------------|
-| Linear problem-solving | Sequential thoughts | Steady progress, scope adjustment |
-| Exploring alternatives | Branching | Multiple paths from decision point |
-| Correcting mistakes | Revision | Reference earlier thought, update conclusion |
-| Complex analysis | Mixed | Combine all features as needed |
-
-## Tips for Effective Use
-
-1. **Start broad, narrow down**: Early thoughts explore problem space, later thoughts dive into specifics
-2. **Show your work**: Document reasoning process, not just conclusions
-3. **Revise when wrong**: Don't continue down incorrect path—backtrack and correct
-4. **Branch at crossroads**: When facing clear alternatives, explore each systematically
-5. **Adjust dynamically**: Change `totalThoughts` as understanding evolves
-6. **End decisively**: Final thought should summarize conclusion and next actions

package/.agent/skills/server-management/SKILL.md

@@ -1,161 +0,0 @@
----
-name: server-management
-description: Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# Server Management
-
-> Server management principles for production operations.
-> **Learn to THINK, not memorize commands.**
-
----
-
-## 1. Process Management Principles
-
-### Tool Selection
-
-| Scenario | Tool |
-|----------|------|
-| **Node.js app** | PM2 (clustering, reload) |
-| **Any app** | systemd (Linux native) |
-| **Containers** | Docker/Podman |
-| **Orchestration** | Kubernetes, Docker Swarm |
-
-### Process Management Goals
-
-| Goal | What It Means |
-|------|---------------|
-| **Restart on crash** | Auto-recovery |
-| **Zero-downtime reload** | No service interruption |
-| **Clustering** | Use all CPU cores |
-| **Persistence** | Survive server reboot |
-
----
-
-## 2. Monitoring Principles
-
-### What to Monitor
-
-| Category | Key Metrics |
-|----------|-------------|
-| **Availability** | Uptime, health checks |
-| **Performance** | Response time, throughput |
-| **Errors** | Error rate, types |
-| **Resources** | CPU, memory, disk |
-
-### Alert Severity Strategy
-
-| Level | Response |
-|-------|----------|
-| **Critical** | Immediate action |
-| **Warning** | Investigate soon |
-| **Info** | Review daily |
-
-### Monitoring Tool Selection
-
-| Need | Options |
-|------|---------|
-| Simple/Free | PM2 metrics, htop |
-| Full observability | Grafana, Datadog |
-| Error tracking | Sentry |
-| Uptime | UptimeRobot, Pingdom |
-
----
-
-## 3. Log Management Principles
-
-### Log Strategy
-
-| Log Type | Purpose |
-|----------|---------|
-| **Application logs** | Debug, audit |
-| **Access logs** | Traffic analysis |
-| **Error logs** | Issue detection |
-
-### Log Principles
-
-1. **Rotate logs** to prevent disk fill
-2. **Structured logging** (JSON) for parsing
-3. **Appropriate levels** (error/warn/info/debug)
-4. **No sensitive data** in logs
-
----
-
-## 4. Scaling Decisions
-
-### When to Scale
-
-| Symptom | Solution |
-|---------|----------|
-| High CPU | Add instances (horizontal) |
-| High memory | Increase RAM or fix leak |
-| Slow response | Profile first, then scale |
-| Traffic spikes | Auto-scaling |
-
-### Scaling Strategy
-
-| Type | When to Use |
-|------|-------------|
-| **Vertical** | Quick fix, single instance |
-| **Horizontal** | Sustainable, distributed |
-| **Auto** | Variable traffic |
-
----
-
-## 5. Health Check Principles
-
-### What Constitutes Healthy
-
-| Check | Meaning |
-|-------|---------|
-| **HTTP 200** | Service responding |
-| **Database connected** | Data accessible |
-| **Dependencies OK** | External services reachable |
-| **Resources OK** | CPU/memory not exhausted |
-
-### Health Check Implementation
-
-- Simple: Just return 200
-- Deep: Check all dependencies
-- Choose based on load balancer needs
-
----
-
-## 6. Security Principles
-
-| Area | Principle |
-|------|-----------|
-| **Access** | SSH keys only, no passwords |
-| **Firewall** | Only needed ports open |
-| **Updates** | Regular security patches |
-| **Secrets** | Environment vars, not files |
-| **Audit** | Log access and changes |
-
----
-
-## 7. Troubleshooting Priority
-
-When something's wrong:
-
-1. **Check if running** (process status)
-2. **Check logs** (error messages)
-3. **Check resources** (disk, memory, CPU)
-4. **Check network** (ports, DNS)
-5. **Check dependencies** (database, APIs)
-
----
-
-## 8. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Run as root | Use non-root user |
-| Ignore logs | Set up log rotation |
-| Skip monitoring | Monitor from day one |
-| Manual restarts | Auto-restart config |
-| No backups | Regular backup schedule |
-
----
-
-> **Remember:** A well-managed server is boring. That's the goal.

package/.agent/skills/skill-creator/LICENSE.txt

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.