[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AXAZR79ZW1X1NPCSD8DBZT":3,"skill-same:01M7AXAZR79ZW1X1NPCSD8DBZT":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":30,"commitSha":31,"skillDirectory":5,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7AXAZR79ZW1X1NPCSD8DBZT","architecture-review",null,"Analyse technical, code, and implementation design decisions before building. Runs 7 architectural frameworks (SWOT, GAP, SEARCH, STRIDE, ATAM, C4, ADR) against a proposed change to surface risks, tradeoffs, and gaps before any code is written. Pass a description of the change as argument (e.g., \"add marketplace skill routing\", \"refactor queue to use Redis streams\").","FREELABEL\u002Firis-skills","FREELABEL","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44075877?v=4","01M7AXATW82ET63TF3KWF42N76","01M7AXATWXNZ6GKS9GZGHJ9HE4",0,"MIT","https:\u002F\u002Fgithub.com\u002FFREELABEL\u002Firis-skills\u002Fblob\u002Fmain\u002Farchitecture-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: architecture-review\ndescription: Analyse technical, code, and implementation design decisions before building. Runs 7 architectural frameworks (SWOT, GAP, SEARCH, STRIDE, ATAM, C4, ADR) against a proposed change to surface risks, tradeoffs, and gaps before any code is written. Pass a description of the change as argument (e.g., \"add marketplace skill routing\", \"refactor queue to use Redis streams\").\nallowed-tools:\n  - Read\n  - Grep\n  - Glob\n  - Bash\n  - Agent\n  - Task\n---\n\n# Architecture Review — Pre-Implementation Analysis Skill\n\nRun a structured architectural analysis on a proposed technical change **before** writing any code. The goal is to catch design flaws, security holes, scaling limits, and migration gaps upfront.\n\n## Arguments\n\n`$ARGUMENTS` — Description of the proposed change, feature, or design decision to analyse.\n\nExamples:\n- `\u002Farchitecture-review add marketplace skill execution to V6ToolRegistry`\n- `\u002Farchitecture-review migrate queue backend from database to Redis streams`\n- `\u002Farchitecture-review add multi-tenant secret isolation for installed workflows`\n- `\u002Farchitecture-review refactor ReactLoopService checkpointing to be async`\n\n---\n\n## How This Skill Works\n\nWhen invoked, run **all 7 frameworks** against the proposed change. For each framework, read the relevant source files to ground the analysis in actual code — never speculate about implementation details without reading them first.\n\nOutput a single structured report with all 7 sections, then a final **Go \u002F No-Go \u002F Conditional Go** recommendation.\n\n---\n\n## Framework 1: SWOT Analysis — Strategic Viability\n\nEvaluate the proposed change from a strategic perspective.\n\n| Category | What to assess |\n|----------|---------------|\n| **Strengths** | What existing code\u002Fpatterns does this leverage? How much reuse vs new code? What safety mechanisms does it inherit? |\n| **Weaknesses** | What's brittle, hardcoded, or fragile in the approach? What coupling does it introduce? |\n| **Opportunities** | What future capabilities does this unlock? Revenue, scale, or ecosystem benefits? |\n| **Threats** | What could go wrong in production? Data leaks, race conditions, sync drift, breaking changes? |\n\n**Source check**: Read the files that will be modified. Identify the exact functions\u002Fclasses affected.\n\n---\n\n## Framework 2: GAP Analysis — Transition Planning\n\nMap the journey from current state to target state.\n\n1. **Current State**: What exists today? Read the actual code. What does it do, what doesn't it do?\n2. **Target State**: What should exist after this change? Be specific about behaviour, not just structure.\n3. **The Gap**: What's missing? List each discrete piece of work.\n4. **Bridge (Action Plan)**: Ordered steps to close the gap. Flag any steps that require migrations, env var changes, or cross-service coordination.\n\n**Source check**: Read the current implementation files. Identify what already exists vs what needs building.\n\n---\n\n## Framework 3: SEARCH — System Traits Assessment\n\nEvaluate 6 non-functional requirements. Rate each as Low \u002F Medium \u002F High \u002F Exceptional with a one-line justification.\n\n| Trait | Question |\n|-------|----------|\n| **S — Scalability** | Does this change scale horizontally? What's the bottleneck (DB writes, memory, API calls)? |\n| **E — Extensibility** | Can future developers extend this without modifying the core? Is it pluggable? |\n| **A — Availability** | What happens when a dependency fails? Is there a fallback? Graceful degradation? |\n| **R — Reliability** | Can this produce incorrect results silently? What invariants could be violated? |\n| **C — Consistency** | In concurrent\u002Fasync scenarios, can state become inconsistent? Race conditions? |\n| **H — Health \u002F Observability** | Can we tell if this is working? Logs, metrics, health checks, alerts? |\n\n---\n\n## Framework 4: STRIDE — Threat Modelling\n\nFor each STRIDE category, assess whether the proposed change introduces or mitigates the threat. Only flag categories that are **actually relevant** — skip categories with no meaningful exposure.\n\n| Threat | Definition | Assessment approach |\n|--------|-----------|-------------------|\n| **Spoofing** | Faking identity | Can an unauthorized actor trigger this? Are auth checks in place? |\n| **Tampering** | Modifying data | Can inputs\u002Fstate be manipulated to produce unintended behaviour? |\n| **Repudiation** | Denying actions | Is there an audit trail? Can we prove what happened? |\n| **Information Disclosure** | Data leaks | Could secrets, PII, or internal state leak across tenant boundaries? |\n| **Denial of Service** | Resource exhaustion | Can this be abused to exhaust CPU, memory, DB connections, API quotas? |\n| **Elevation of Privilege** | Gaining access | Could this bypass permission checks or escalate user capabilities? |\n\n**Source check**: Read auth middleware, secret management, and permission checks in the affected code paths.\n\n---\n\n## Framework 5: ATAM — Architecture Tradeoff Analysis\n\nIdentify the **top 3 architectural decisions** in the proposed change. For each:\n\n1. **Decision**: What architectural choice is being made?\n2. **Optimises for**: Which quality attribute does this favour? (performance, reliability, extensibility, etc.)\n3. **Trades off**: Which quality attribute suffers? Be specific about the cost.\n4. **Sensitivity point**: Under what conditions does this tradeoff become painful?\n5. **Mitigation**: What could reduce the downside without losing the upside?\n\n---\n\n## Framework 6: C4 Model — Structural Impact\n\nZoom through 4 levels to show where this change fits architecturally. Only go as deep as needed — skip levels that aren't affected.\n\n- **Level 1 — Context**: How does this change affect system boundaries? New external dependencies? Changed data flows between systems?\n- **Level 2 — Containers**: Which services\u002Fcontainers are affected? (iris-api, fl-api, fl-elon-web-ui, n8n, daemon, etc.)\n- **Level 3 — Components**: Which modules\u002Fservices\u002Fcontrollers within those containers are modified?\n- **Level 4 — Code**: Which specific classes, methods, or functions change? What's the call chain?\n\nPresent as a concise list, not a diagram. Reference actual file paths.\n\n---\n\n## Framework 7: ADR — Architecture Decision Record\n\nWrite a draft ADR for the most significant decision in this change.\n\n```\n## ADR: [Title]\n\n### Status\nProposed\n\n### Context\n[Why is this decision needed? What problem does it solve?]\n\n### Decision\n[What are we doing? Be specific about the implementation approach.]\n\n### Consequences\n**Positive:**\n- [benefit 1]\n- [benefit 2]\n\n**Negative:**\n- [cost 1]\n- [cost 2]\n\n**Risks:**\n- [risk + mitigation]\n```\n\n---\n\n## Final Verdict\n\nAfter all 7 frameworks, deliver a clear recommendation:\n\n### Recommendation: **[Go \u002F No-Go \u002F Conditional Go]**\n\n**If Go**: List the implementation order (what to build first, what to defer).\n\n**If Conditional Go**: List the specific conditions that must be met before proceeding (e.g., \"add migration for X first\", \"verify Y doesn't break Z\").\n\n**If No-Go**: Explain why and propose an alternative approach.\n\n### Critical Risks (if any)\n- Numbered list of risks that could cause production incidents if ignored.\n\n### Suggested Implementation Order\n1. Step 1 — [what + why first]\n2. Step 2 — [what + why second]\n3. ...\n\n---\n\n## Research Protocol\n\nBefore writing the analysis, you MUST:\n\n1. **Read the affected files** — Use Glob\u002FGrep\u002FRead to find and examine the actual code that will change.\n2. **Check for existing patterns** — Search for how similar problems are already solved in the codebase.\n3. **Verify assumptions** — If the proposal mentions a table, class, or config, confirm it exists and check its current state.\n4. **Check recent git history** — Look at recent commits to the affected files to understand momentum and context.\n\nDo NOT speculate about code you haven't read. If you can't find a file or class mentioned in the proposal, flag it explicitly.\n","# Architecture Review — Pre-Implementation Analysis Skill\n\nRun a structured architectural analysis on a proposed technical change **before** writing any code. The goal is to catch design flaws, security holes, scaling limits, and migration gaps upfront.\n\n## Arguments\n\n`$ARGUMENTS` — Description of the proposed change, feature, or design decision to analyse.\n\nExamples:\n- `\u002Farchitecture-review add marketplace skill execution to V6ToolRegistry`\n- `\u002Farchitecture-review migrate queue backend from database to Redis streams`\n- `\u002Farchitecture-review add multi-tenant secret isolation for installed workflows`\n- `\u002Farchitecture-review refactor ReactLoopService checkpointing to be async`\n\n---\n\n## How This Skill Works\n\nWhen invoked, run **all 7 frameworks** against the proposed change. For each framework, read the relevant source files to ground the analysis in actual code — never speculate about implementation details without reading them first.\n\nOutput a single structured report with all 7 sections, then a final **Go \u002F No-Go \u002F Conditional Go** recommendation.\n\n---\n\n## Framework 1: SWOT Analysis — Strategic Viability\n\nEvaluate the proposed change from a strategic perspective.\n\n| Category | What to assess |\n|----------|---------------|\n| **Strengths** | What existing code\u002Fpatterns does this leverage? How much reuse vs new code? What safety mechanisms does it inherit? |\n| **Weaknesses** | What's brittle, hardcoded, or fragile in the approach? What coupling does it introduce? |\n| **Opportunities** | What future capabilities does this unlock? Revenue, scale, or ecosystem benefits? |\n| **Threats** | What could go wrong in production? Data leaks, race conditions, sync drift, breaking changes? |\n\n**Source check**: Read the files that will be modified. Identify the exact functions\u002Fclasses affected.\n\n---\n\n## Framework 2: GAP Analysis — Transition Planning\n\nMap the journey from current state to target state.\n\n1. **Current State**: What exists today? Read the actual code. What does it do, what doesn't it do?\n2. **Target State**: What should exist after this change? Be specific about behaviour, not just structure.\n3. **The Gap**: What's missing? List each discrete piece of work.\n4. **Bridge (Action Plan)**: Ordered steps to close the gap. Flag any steps that require migrations, env var changes, or cross-service coordination.\n\n**Source check**: Read the current implementation files. Identify what already exists vs what needs building.\n\n---\n\n## Framework 3: SEARCH — System Traits Assessment\n\nEvaluate 6 non-functional requirements. Rate each as Low \u002F Medium \u002F High \u002F Exceptional with a one-line justification.\n\n| Trait | Question |\n|-------|----------|\n| **S — Scalability** | Does this change scale horizontally? What's the bottleneck (DB writes, memory, API calls)? |\n| **E — Extensibility** | Can future developers extend this without modifying the core? Is it pluggable? |\n| **A — Availability** | What happens when a dependency fails? Is there a fallback? Graceful degradation? |\n| **R — Reliability** | Can this produce incorrect results silently? What invariants could be violated? |\n| **C — Consistency** | In concurrent\u002Fasync scenarios, can state become inconsistent? Race conditions? |\n| **H — Health \u002F Observability** | Can we tell if this is working? Logs, metrics, health checks, alerts? |\n\n---\n\n## Framework 4: STRIDE — Threat Modelling\n\nFor each STRIDE category, assess whether the proposed change introduces or mitigates the threat. Only flag categories that are **actually relevant** — skip categories with no meaningful exposure.\n\n| Threat | Definition | Assessment approach |\n|--------|-----------|-------------------|\n| **Spoofing** | Faking identity | Can an unauthorized actor trigger this? Are auth checks in place? |\n| **Tampering** | Modifying data | Can inputs\u002Fstate be manipulated to produce unintended behaviour? |\n| **Repudiation** | Denying actions | Is there an audit trail? Can we prove what happened? |\n| **Information Disclosure** | Data leaks | Could secrets, PII, or internal state leak across tenant boundaries? |\n| **Denial of Service** | Resource exhaustion | Can this be abused to exhaust CPU, memory, DB connections, API quotas? |\n| **Elevation of Privilege** | Gaining access | Could this bypass permission checks or escalate user capabilities? |\n\n**Source check**: Read auth middleware, secret management, and permission checks in the affected code paths.\n\n---\n\n## Framework 5: ATAM — Architecture Tradeoff Analysis\n\nIdentify the **top 3 architectural decisions** in the proposed change. For each:\n\n1. **Decision**: What architectural choice is being made?\n2. **Optimises for**: Which quality attribute does this favour? (performance, reliability, extensibility, etc.)\n3. **Trades off**: Which quality attribute suffers? Be specific about the cost.\n4. **Sensitivity point**: Under what conditions does this tradeoff become painful?\n5. **Mitigation**: What could reduce the downside without losing the upside?\n\n---\n\n## Framework 6: C4 Model — Structural Impact\n\nZoom through 4 levels to show where this change fits architecturally. Only go as deep as needed — skip levels that aren't affected.\n\n- **Level 1 — Context**: How does this change affect system boundaries? New external dependencies? Changed data flows between systems?\n- **Level 2 — Containers**: Which services\u002Fcontainers are affected? (iris-api, fl-api, fl-elon-web-ui, n8n, daemon, etc.)\n- **Level 3 — Components**: Which modules\u002Fservices\u002Fcontrollers within those containers are modified?\n- **Level 4 — Code**: Which specific classes, methods, or functions change? What's the call chain?\n\nPresent as a concise list, not a diagram. Reference actual file paths.\n\n---\n\n## Framework 7: ADR — Architecture Decision Record\n\nWrite a draft ADR for the most significant decision in this change.\n\n```\n## ADR: [Title]\n\n### Status\nProposed\n\n### Context\n[Why is this decision needed? What problem does it solve?]\n\n### Decision\n[What are we doing? Be specific about the implementation approach.]\n\n### Consequences\n**Positive:**\n- [benefit 1]\n- [benefit 2]\n\n**Negative:**\n- [cost 1]\n- [cost 2]\n\n**Risks:**\n- [risk + mitigation]\n```\n\n---\n\n## Final Verdict\n\nAfter all 7 frameworks, deliver a clear recommendation:\n\n### Recommendation: **[Go \u002F No-Go \u002F Conditional Go]**\n\n**If Go**: List the implementation order (what to build first, what to defer).\n\n**If Conditional Go**: List the specific conditions that must be met before proceeding (e.g., \"add migration for X first\", \"verify Y doesn't break Z\").\n\n**If No-Go**: Explain why and propose an alternative approach.\n\n### Critical Risks (if any)\n- Numbered list of risks that could cause production incidents if ignored.\n\n### Suggested Implementation Order\n1. Step 1 — [what + why first]\n2. Step 2 — [what + why second]\n3. ...\n\n---\n\n## Research Protocol\n\nBefore writing the analysis, you MUST:\n\n1. **Read the affected files** — Use Glob\u002FGrep\u002FRead to find and examine the actual code that will change.\n2. **Check for existing patterns** — Search for how similar problems are already solved in the codebase.\n3. **Verify assumptions** — If the proposal mentions a table, class, or config, confirm it exists and check its current state.\n4. **Check recent git history** — Look at recent commits to the affected files to understand momentum and context.\n\nDo NOT speculate about code you haven't read. If you can't find a file or class mentioned in the proposal, flag it explicitly.\n",{"name":5,"description":7,"allowed-tools":23},[24,25,26,27,28,29],"Read","Grep","Glob","Bash","Agent","Task","main","a038054a4eb50d830c84f58cc68a03cd5c163e0c","https:\u002F\u002Fgithub.com\u002FFREELABEL\u002Firis-skills","https:\u002F\u002Fgithub.com\u002FFREELABEL","2026-08-21 22:16:57",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add FREELABEL\u002Firis-skills --skill architecture-review",{"tool":41,"command":42},"bunx","bunx skills add FREELABEL\u002Firis-skills --skill architecture-review",{"tool":44,"command":45},"pnpm","pnpm dlx skills add FREELABEL\u002Firis-skills --skill architecture-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFREELABEL\u002Firis-skills\u002Fblob\u002Fmain\u002Farchitecture-review\u002FSKILL.md",true,[],[50,57],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7AXB55A8JZTGWF5JNS9H7W6","health-check","Check production health across all services and report status","https:\u002F\u002Fgithub.com\u002FFREELABEL\u002Firis-skills\u002Fblob\u002Fmain\u002Fhealth-check\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7AXAWET2D86BRBARKPHGVXE","agentic-loop","Loop engineering reference — run one self-prompting agentic-loop cycle (orchestrator → discover → plan → fan-out specialists → verify against goal → synthesize → write memory), then optionally wire the weekly schedule. Reproduces the Builder\u002FScout\u002FGrowth demo and generalizes to any goal.","https:\u002F\u002Fgithub.com\u002FFREELABEL\u002Firis-skills\u002Fblob\u002Fmain\u002Fagentic-loop\u002FSKILL.md",[],[]]