[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-jwynia-agile-workflow-en":3,"guides-for-jwynia-agile-workflow":223,"similar-k17dkjvzgg6cxjhh7hmz742gq5866hnf":224},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":21,"identity":190,"isFallback":185,"parentExtension":195,"providers":196,"relations":200,"repo":202,"workflow":220},1778053622473.6677,"k17dkjvzgg6cxjhh7hmz742gq5866hnf",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":12,"sourceUrl":13,"tags":14},"Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control. This skill should be used when the user asks to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wants guided step-by-step development assistance. Platform-agnostic git-only workflow without PR integration. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, merge, standup, retrospective, git.",{},"Agile Workflow Orchestrator","https://github.com/jwynia/agent-skills/tree/HEAD/skills/tech/development/workflow/agile-workflow",[15,16,17,18,19,20],"agile","workflow","git","development","task-management","orchestration",{"_creationTime":22,"_id":23,"extensionId":5,"locale":24,"result":25,"trustSignals":178,"workflow":188},1778054012697.029,"kn7chh06bvanvcs1mhx0pzbdzd8678j1","en",{"checks":26,"evaluatedAt":168,"extensionSummary":169,"promptVersionExtension":170,"promptVersionScoring":171,"rationale":172,"score":173,"summary":174,"tags":175,"targetMarket":176,"tier":177},[27,32,35,38,42,45,49,54,57,60,64,69,72,76,79,82,85,88,91,94,98,102,106,110,114,117,120,123,127,130,133,136,139,142,146,149,152,155,158,161,165],{"category":28,"check":29,"severity":30,"summary":31},"Practical Utility","Problem relevance","pass","The description clearly names a concrete user problem: orchestrating agile development workflows with checkpoint-based flow control, addressing the need for guided step-by-step development assistance.",{"category":28,"check":33,"severity":30,"summary":34},"Unique selling proposition","The skill provides a unique selling proposition by offering checkpoint-based flow control for orchestrating agile workflows, going beyond simple command execution with guided step-by-step assistance and managing complex task cycles.",{"category":28,"check":36,"severity":30,"summary":37},"Production readiness","The extension covers the complete lifecycle of an agile workflow, from task selection and implementation to review, merge, and status updates, making it production-ready for git-only workflows.",{"category":39,"check":40,"severity":30,"summary":41},"Scope","Single responsibility principle","The extension focuses on orchestrating agile development workflows with a git-only approach, clearly defining its scope and not extending into unrelated domains like PR integration or general code execution.",{"category":39,"check":43,"severity":30,"summary":44},"Description quality","The description is accurate, concise, readable, and accurately reflects the skill's behavior, clearly outlining its purpose and when to use it.",{"category":46,"check":47,"severity":30,"summary":48},"Invocation","Scoped tools","The skill utilizes narrow verb-noun specialist tools like `sync`, `groom`, `next`, `implement`, etc., making them easier for the agent to select and reducing attack surface.",{"category":50,"check":51,"severity":52,"summary":53},"Documentation","Configuration & parameter reference","info","Parameters like `--phase`, `--task`, and `--dry-run` are documented via invocation patterns, but there's no explicit mention of default values or precedence order for any configuration if it were to exist beyond command-line arguments.",{"category":39,"check":55,"severity":30,"summary":56},"Tool naming","All tool names (`sync`, `groom`, `next`, `implement`, `review-code`, `merge-complete`, etc.) are descriptive, verb-noun pairs within the declared agile development domain.",{"category":39,"check":58,"severity":30,"summary":59},"Minimal I/O surface","Tools appear to have minimal input schemas and focused outputs, primarily dealing with task IDs, status reports, and review summaries, without excessive or undocumented fields.",{"category":61,"check":62,"severity":30,"summary":63},"License","License usability","The license is MIT, a permissive open-source license, and is clearly declared in the SKILL.md frontmatter.",{"category":65,"check":66,"severity":67,"summary":68},"Maintenance","Commit recency","not_applicable","No commit history is available for this evaluation, so recency cannot be determined.",{"category":65,"check":70,"severity":67,"summary":71},"Dependency Management","No third-party dependencies are explicitly listed or managed by this skill; it relies on git and potentially standard Node.js environment capabilities.",{"category":73,"check":74,"severity":30,"summary":75},"Security","Secret Management","The skill orchestrates git commands and workflow steps; it does not appear to handle or expose secrets directly. Commands executed are standard git operations.",{"category":73,"check":77,"severity":30,"summary":78},"Injection","The skill uses scoped tools and predefined commands; it does not load external data as instructions or fetch remote content dynamically for execution.",{"category":73,"check":80,"severity":30,"summary":81},"Transitive Supply-Chain Grenades","The skill relies on local git commands and bundled script references, with no runtime downloads or remote execution of arbitrary code.",{"category":73,"check":83,"severity":30,"summary":84},"Sandbox Isolation","The skill operates within the standard git workflow and project directory, not attempting to modify files outside its designated scope.",{"category":73,"check":86,"severity":30,"summary":87},"Sandbox escape primitives","No detached-process spawns or deny-retry loops were detected in the skill's operational description.",{"category":73,"check":89,"severity":30,"summary":90},"Data Exfiltration","The skill orchestrates local development tasks and does not appear to make outbound calls that could exfiltrate confidential data.",{"category":73,"check":92,"severity":30,"summary":93},"Hidden Text Tricks","The bundled files and markdown content do not contain any hidden-steering tricks, invisible characters, or obfuscated instructions.",{"category":95,"check":96,"severity":30,"summary":97},"Hooks","Opaque code execution","The skill's logic is described in clear markdown and relies on standard command-line tools; there is no obfuscated code, base64 payloads, or runtime fetched scripts.",{"category":99,"check":100,"severity":30,"summary":101},"Portability","Structural Assumption","The skill relies on standard git commands and the presence of a `context-network/` directory, which is a documented prerequisite rather than an assumption of specific user project organization.",{"category":103,"check":104,"severity":67,"summary":105},"Trust","Issues Attention","No issue tracker data is available for this evaluation.",{"category":107,"check":108,"severity":30,"summary":109},"Versioning","Release Management","A version ('2.0') is clearly declared in the SKILL.md frontmatter.",{"category":111,"check":112,"severity":52,"summary":113},"Code Execution","Validation","While the skill orchestrates commands and uses structured checkpoints, there's no explicit mention or evidence of a schema library being used for input validation beyond standard command-line argument parsing.",{"category":73,"check":115,"severity":30,"summary":116},"Unguarded Destructive Operations","The skill involves git operations like merging and branch manipulation, but these are standard development actions and are typically guarded by user confirmation prompts at checkpoints or require explicit user commands.",{"category":111,"check":118,"severity":30,"summary":119},"Error Handling","The documentation details error handling at checkpoints, including specific error messages, suggested resolutions, and the ability to resume workflows, indicating robust error management.",{"category":111,"check":121,"severity":67,"summary":122},"Logging","The skill focuses on orchestrating git commands and workflow steps; it does not appear to perform destructive actions or outbound calls that would necessitate a local audit file.",{"category":124,"check":125,"severity":67,"summary":126},"Compliance","GDPR","The skill operates on project code and metadata, not personal data.",{"category":124,"check":128,"severity":30,"summary":129},"Target market","The skill is described as platform-agnostic and git-only, with no regional or jurisdictional logic detected, making its target market global.",{"category":99,"check":131,"severity":30,"summary":132},"Runtime stability","The skill relies on standard git commands and assumes a POSIX-like environment for its operations, with no explicit assumptions about specific editors or custom runtimes.",{"category":46,"check":134,"severity":30,"summary":135},"Precise Purpose","The description clearly states the skill orchestrates agile development workflows using git-only commands and provides specific 'when to use' and 'do not use' scenarios, defining its precise purpose.",{"category":46,"check":137,"severity":30,"summary":138},"Concise Frontmatter","The frontmatter is dense and self-contained, summarizing the core capability and including trigger phrases within a reasonable character limit.",{"category":50,"check":140,"severity":30,"summary":141},"Concise Body","The SKILL.md body is well-structured, under the ~500 line limit, and delegates deeper material like command references and phase details to separate markdown files.",{"category":143,"check":144,"severity":30,"summary":145},"Context","Progressive Disclosure","Detailed procedures for commands and phases are appropriately separated into `references/` files, linked via relative paths from the main SKILL.md, adhering to progressive disclosure.",{"category":143,"check":147,"severity":67,"summary":148},"Forked exploration","The skill orchestrates a linear workflow rather than deep exploration, so `context: fork` is not applicable.",{"category":28,"check":150,"severity":30,"summary":151},"Usage examples","Sufficient end-to-end examples are provided for task cycles, daily sequences, and sprint ceremonies, demonstrating invocation and expected flow.",{"category":28,"check":153,"severity":30,"summary":154},"Edge cases","The documentation addresses edge cases like merge conflicts, test failures, and stale worktrees, providing recovery steps and documenting limitations.",{"category":111,"check":156,"severity":67,"summary":157},"Tool Fallback","The skill relies on standard git commands and does not reference external tools like MCP servers that would require a fallback mechanism.",{"category":99,"check":159,"severity":30,"summary":160},"Stack assumptions","The skill assumes a git-enabled environment and a POSIX-like shell for its commands, with clear documentation for prerequisites and invocation patterns.",{"category":162,"check":163,"severity":30,"summary":164},"Safety","Halt on unexpected state","The skill detects unexpected states (e.g., worktree mismatch, unmerged branches) and halts the workflow with clear reports and suggested resolutions, preventing destructive actions on incorrect states.",{"category":99,"check":166,"severity":30,"summary":167},"Cross-skill coupling","The skill is self-contained for its git-only workflow and explicitly references related skills like `gitea-workflow` or `github-agile` for PR-based workflows, avoiding implicit coupling.",1778053899628,"This skill manages the entire lifecycle of agile software development tasks in a git-only environment. It provides structured sequences for daily standups, sprint planning and retrospectives, and detailed task cycles including implementation, review, and merging, all while maintaining a context network for documentation and knowledge capture.","2.0.0","3.4.0","The 'agile-workflow' skill is exceptionally well-documented and structured, covering all aspects of an agile development lifecycle with clear commands, checkpoints, and error handling. It adheres to best practices for modularity and progressive disclosure. The only minor point for improvement is the lack of explicit documentation on default parameter values and configuration precedence, hence the high score.",95,"A comprehensive skill for orchestrating agile development workflows using git-only commands, providing structure from task selection to merge and status updates.",[15,16,17,18,19,20],"global","verified",{"codeQuality":179,"collectedAt":180,"documentation":181,"maintenance":183,"security":184,"testCoverage":187},{},1778053881489,{"descriptionLength":182,"readmeSize":8},534,{},{"hasNpmPackage":185,"license":186,"smitheryVerified":185},false,"MIT",{"hasCi":185,"hasTests":185},{"updatedAt":189},1778054012696,{"githubOwner":191,"githubRepo":192,"locale":24,"slug":193,"type":194},"jwynia","agent-skills","agile-workflow","skill",null,{"extract":197,"llm":199},{"commitSha":198,"license":186},"e02ec7e226a6e4f8419fd3b88a1d8e472d421b32",{"promptVersionExtension":170,"promptVersionScoring":171,"score":173,"targetMarket":176,"tier":177},{"repoId":201},"kd7efn3mprpa8rd8vm5hw5ebzx864fph",{"_creationTime":203,"_id":201,"identity":204,"providers":206,"workflow":217},1777995558409.897,{"githubOwner":191,"githubRepo":192,"sourceUrl":205},"https://github.com/jwynia/agent-skills",{"discover":207,"github":210},{"sources":208},[209],"skills-sh",{"closedIssues90d":8,"forks":211,"openIssues90d":212,"pushedAt":213,"readmeSize":214,"stars":215,"topics":216},10,2,1771900514000,11924,70,[],{"discoverAt":218,"extractAt":219,"githubAt":219,"updatedAt":219},1777995558409,1778053628601,{"anyEnrichmentAt":221,"extractAt":222,"githubAt":221,"llmAt":189,"updatedAt":189},1778053625386,1778053622473,[],[225,246,264,283,311,338],{"_creationTime":226,"_id":227,"community":228,"display":229,"identity":238,"providers":240,"relations":244,"workflow":245},1778053622473.6682,"k171xwg814163s51767b0q0pn1866cwe",{"reviewCount":8},{"description":230,"installMethods":231,"name":232,"sourceUrl":233,"tags":234},"Orchestrate multiple worker agents to implement groomed tasks in Gitea repositories. Use when multiple ready tasks need implementation, when you want autonomous multi-task execution, or when coordinating batch development work with Gitea. Keywords: coordinator, orchestrator, multi-task, parallel, workers, batch, autonomous, gitea, tea.",{},"Gitea Coordinator","https://github.com/jwynia/agent-skills/tree/HEAD/skills/tech/development/workflow/gitea-coordinator",[235,20,236,15,18,16,237],"gitea","automation","multi-agent",{"githubOwner":191,"githubRepo":192,"locale":24,"slug":239,"type":194},"gitea-coordinator",{"extract":241,"llm":242},{"commitSha":198,"license":186},{"promptVersionExtension":170,"promptVersionScoring":171,"score":243,"targetMarket":176,"tier":177},98,{"repoId":201},{"anyEnrichmentAt":221,"extractAt":222,"githubAt":221,"llmAt":189,"updatedAt":189},{"_creationTime":247,"_id":248,"community":249,"display":250,"identity":257,"providers":259,"relations":262,"workflow":263},1778053622473.6672,"k178b0dafhyecx3y6cbxkne8mh866zc4",{"reviewCount":8},{"description":251,"installMethods":252,"name":253,"sourceUrl":254,"tags":255},"Orchestrate multiple worker agents to implement groomed tasks. Use when multiple ready tasks need implementation, when you want autonomous multi-task execution, or when coordinating batch development work. Keywords: coordinator, orchestrator, multi-task, parallel, workers, batch, autonomous.",{},"Agile Coordinator","https://github.com/jwynia/agent-skills/tree/HEAD/skills/tech/development/workflow/agile-coordinator",[15,16,20,256,17,236],"developer-tools",{"githubOwner":191,"githubRepo":192,"locale":24,"slug":258,"type":194},"agile-coordinator",{"extract":260,"llm":261},{"commitSha":198,"license":186},{"promptVersionExtension":170,"promptVersionScoring":171,"score":243,"targetMarket":176,"tier":177},{"repoId":201},{"anyEnrichmentAt":221,"extractAt":222,"githubAt":221,"llmAt":189,"updatedAt":189},{"_creationTime":265,"_id":266,"community":267,"display":268,"identity":276,"providers":278,"relations":281,"workflow":282},1778053622473.6692,"k17e2jngyq2nkmw93gajm8116h867cx5",{"reviewCount":8},{"description":269,"installMethods":270,"name":271,"sourceUrl":272,"tags":273},"Diagnose GitHub-driven agile workflow problems and guide feature branch development",{},"GitHub Agile: Feature Branch Development with Context Networks","https://github.com/jwynia/agent-skills/tree/HEAD/skills/tech/development/workflow/github-agile",[274,15,16,18,275,17],"github","cli",{"githubOwner":191,"githubRepo":192,"locale":24,"slug":277,"type":194},"github-agile",{"extract":279,"llm":280},{"commitSha":198,"license":186},{"promptVersionExtension":170,"promptVersionScoring":171,"score":173,"targetMarket":176,"tier":177},{"repoId":201},{"anyEnrichmentAt":221,"extractAt":222,"githubAt":221,"llmAt":189,"updatedAt":189},{"_creationTime":284,"_id":285,"community":286,"display":287,"identity":296,"providers":300,"relations":305,"workflow":307},1778053100136.2383,"k1753vf5cqqy17a43rxzq74p09866pde",{"reviewCount":8},{"description":288,"installMethods":289,"name":290,"sourceUrl":291,"tags":292},"Extension from bytedance/deer-flow",{},"DeerFlow Smoke Test","https://github.com/bytedance/deer-flow/tree/HEAD/.agent/skills/smoke-test",[293,18,294,295,16],"testing","docker","bash",{"githubOwner":297,"githubRepo":298,"locale":24,"slug":299,"type":194},"bytedance","deer-flow","smoke-test",{"extract":301,"llm":303},{"commitSha":302,"license":186},"1336872b15c25d45ebcb7c1cf72369c2bdd53187",{"promptVersionExtension":170,"promptVersionScoring":171,"score":304,"targetMarket":176,"tier":177},96,{"repoId":306},"kd789sm7egx1h0t1jag6zzhcq98656wv",{"anyEnrichmentAt":308,"extractAt":309,"githubAt":308,"llmAt":310,"updatedAt":310},1778053101076,1778053100136,1778053169012,{"_creationTime":312,"_id":313,"community":314,"display":315,"identity":324,"providers":328,"relations":332,"workflow":334},1778054741404.8755,"k17f34v6c7vmvgxab7k2xy2xrh8666t8",{"reviewCount":8},{"description":316,"installMethods":317,"name":318,"sourceUrl":319,"tags":320},"Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.",{},"Code Review Expert","https://github.com/sanyuan0704/sanyuan-skills/tree/HEAD/skills/code-review-expert",[321,17,322,18,323],"code-review","security","quality-assurance",{"githubOwner":325,"githubRepo":326,"locale":24,"slug":327,"type":194},"sanyuan0704","sanyuan-skills","code-review-expert",{"extract":329,"llm":331},{"commitSha":330,"license":186},"807460aaa6e23313d9e16c397d100130691083a5",{"promptVersionExtension":170,"promptVersionScoring":171,"score":173,"targetMarket":176,"tier":177},{"repoId":333},"kd7ehbmfr6fxv4k4d6h65hev89864gmz",{"anyEnrichmentAt":335,"extractAt":336,"githubAt":335,"llmAt":337,"updatedAt":337},1778054741686,1778054741404,1778054758790,{"_creationTime":339,"_id":340,"community":341,"display":342,"identity":349,"providers":351,"relations":356,"workflow":357},1778053622473.6687,"k172bb1yvvs8qznmk5awew5xvd866wqt",{"reviewCount":8},{"description":343,"installMethods":344,"name":345,"sourceUrl":346,"tags":347},"Orchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.",{},"Gitea Workflow Orchestrator","https://github.com/jwynia/agent-skills/tree/HEAD/skills/tech/development/workflow/gitea-workflow",[235,15,16,348,18,20],"tea-cli",{"githubOwner":191,"githubRepo":192,"locale":24,"slug":350,"type":194},"gitea-workflow",{"extract":352,"llm":353},{"commitSha":198,"license":186},{"promptVersionExtension":170,"promptVersionScoring":171,"score":354,"targetMarket":176,"tier":355},65,"flagged",{"repoId":201},{"anyEnrichmentAt":221,"extractAt":222,"githubAt":221,"llmAt":189,"updatedAt":189}]