[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-jwynia-gitea-workflow-en":3,"guides-for-jwynia-gitea-workflow":224,"similar-k172bb1yvvs8qznmk5awew5xvd866wqt":225},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":21,"identity":191,"isFallback":186,"parentExtension":196,"providers":197,"relations":201,"repo":203,"workflow":221},1778053622473.6687,"k172bb1yvvs8qznmk5awew5xvd866wqt",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":12,"sourceUrl":13,"tags":14},"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",[15,16,17,18,19,20],"gitea","agile","workflow","tea-cli","development","orchestration",{"_creationTime":22,"_id":23,"extensionId":5,"locale":24,"result":25,"trustSignals":179,"workflow":189},1778054012697.0564,"kn761fkn947gagkksey2qwsqjn867d6t","en",{"checks":26,"evaluatedAt":169,"extensionSummary":170,"promptVersionExtension":171,"promptVersionScoring":172,"rationale":173,"score":174,"summary":175,"tags":176,"targetMarket":177,"tier":178},[27,32,35,38,42,45,49,54,57,60,64,69,73,78,81,84,87,90,93,96,99,103,107,111,115,118,121,124,128,131,134,137,140,143,147,150,153,156,159,162,166],{"category":28,"check":29,"severity":30,"summary":31},"Practical Utility","Problem relevance","pass","The displayed description clearly names the problem: orchestrating agile development workflows for Gitea repositories, and specifies the target user and context.",{"category":28,"check":33,"severity":30,"summary":34},"Unique selling proposition","The skill offers significant value over a simple prompt by orchestrating complex, multi-step agile workflows using specific CLI commands and state management, going beyond basic API interaction.",{"category":28,"check":36,"severity":30,"summary":37},"Production readiness","The skill appears production-ready, covering the complete lifecycle of agile development for Gitea, including setup, implementation, review, PR management, and cleanup, with clear prerequisites.",{"category":39,"check":40,"severity":30,"summary":41},"Scope","Single responsibility principle","The skill focuses on orchestrating Gitea development workflows and does not extend into unrelated domains.",{"category":39,"check":43,"severity":30,"summary":44},"Description quality","The description is accurate, concise, and readable, clearly outlining the skill's purpose, use cases, and keywords, and matches the source code's functionality.",{"category":46,"check":47,"severity":30,"summary":48},"Invocation","Scoped tools","The skill uses narrow verb-noun specialist tools for specific actions within the workflow (e.g., sync, implement, review-code), which is optimal for agent selection.",{"category":50,"check":51,"severity":52,"summary":53},"Documentation","Configuration & parameter reference","info","Environment variables like GITEA_URL and GITEA_TOKEN are mentioned as prerequisites but their precedence order and default behaviors (if any) are not explicitly documented.",{"category":39,"check":55,"severity":30,"summary":56},"Tool naming","Tool names like 'sync', 'implement', 'review-code', and 'pr-prep' are descriptive, in kebab-case, and clearly relate to their actions within the Gitea workflow domain.",{"category":39,"check":58,"severity":30,"summary":59},"Minimal I/O surface","The skill's commands accept structured inputs (e.g., task IDs, phases) and its outputs are designed to provide necessary information for workflow progression without excessive detail.",{"category":61,"check":62,"severity":30,"summary":63},"License","License usability","The extension is licensed under MIT, a permissive open-source license, clearly indicated in the SKILL.md frontmatter.",{"category":65,"check":66,"severity":67,"summary":68},"Maintenance","Commit recency","critical","There are no commits on the default branch, indicating the project is likely unmaintained and poses a risk due to potential staleness of dependencies or Gitea API changes.",{"category":65,"check":70,"severity":71,"summary":72},"Dependency Management","not_applicable","The skill does not appear to use external 3rd party dependencies beyond standard CLIs like git and tea, making dependency management checks not applicable.",{"category":74,"check":75,"severity":76,"summary":77},"Security","Secret Management","warning","The skill relies on GITEA_TOKEN and GITEA_URL environment variables for authentication, but there's no explicit mechanism described for handling or redacting these secrets during output, potentially leading to leaks.",{"category":74,"check":79,"severity":30,"summary":80},"Injection","The skill appears to bundle all necessary scripts and data, and its workflow commands are invoked directly rather than relying on fetched or untrusted external content.",{"category":74,"check":82,"severity":30,"summary":83},"Transitive Supply-Chain Grenades","All scripts and logic are contained within the repository bundle, and there are no runtime downloads or execution of external code.",{"category":74,"check":85,"severity":30,"summary":86},"Sandbox Isolation","The skill operates within defined workflows and relies on git and tea CLI commands, with no apparent attempts to access or modify files outside the project or worktree scope.",{"category":74,"check":88,"severity":30,"summary":89},"Sandbox escape primitives","The bundled scripts do not appear to use primitives like 'nohup' or background process spawns that could lead to sandbox escapes.",{"category":74,"check":91,"severity":30,"summary":92},"Data Exfiltration","The skill's purpose is workflow orchestration and it does not appear to involve reading or submitting confidential data to third parties.",{"category":74,"check":94,"severity":30,"summary":95},"Hidden Text Tricks","Bundled files do not contain hidden text tricks, invisible Unicode characters, or other obfuscation methods designed to steer the model without curator visibility.",{"category":74,"check":97,"severity":30,"summary":98},"Opaque code execution","The skill's scripts are written in plain shell and are directly executable, with no signs of base64 payloads, obfuscated JavaScript, or runtime code fetching.",{"category":100,"check":101,"severity":30,"summary":102},"Portability","Structural Assumption","The skill makes assumptions about project layout (e.g., context network at `context-network/backlog/`), but these are documented and standard for this type of workflow skill.",{"category":104,"check":105,"severity":71,"summary":106},"Trust","Issues Attention","No issues data available from the repository.",{"category":108,"check":109,"severity":76,"summary":110},"Versioning","Release Management","The SKILL.md frontmatter declares a version '1.0', but there are no GitHub releases or CHANGELOG.md, and the lack of commits makes this version signal unreliable.",{"category":112,"check":113,"severity":52,"summary":114},"Code Execution","Validation","While the skill uses commands and arguments, it does not explicitly mention or demonstrate the use of a schema validation library for all inputs and outputs.",{"category":74,"check":116,"severity":30,"summary":117},"Unguarded Destructive Operations","Operations like merging PRs and updating main branch documentation are guarded by workflow steps and confirmations, preventing accidental destructive actions.",{"category":112,"check":119,"severity":30,"summary":120},"Error Handling","The skill's documentation and reference files detail error handling procedures, including checkpoint-based error reporting and recovery steps.",{"category":112,"check":122,"severity":71,"summary":123},"Logging","The skill's purpose is workflow orchestration and does not involve destructive actions or outbound calls that would necessitate a local audit log.",{"category":125,"check":126,"severity":71,"summary":127},"Compliance","GDPR","The skill operates on code and task management data, not personal data, so GDPR considerations are not directly applicable.",{"category":125,"check":129,"severity":30,"summary":130},"Target market","The skill is Gitea-specific and mentions general development practices, with no regional or jurisdictional limitations detected; targetMarket is set to 'global'.",{"category":100,"check":132,"severity":30,"summary":133},"Runtime stability","The skill relies on standard CLIs (git, tea) and shell scripting, which are generally portable across POSIX environments, with no explicit OS or editor assumptions.",{"category":46,"check":135,"severity":30,"summary":136},"Precise Purpose","The description clearly states the skill's purpose (orchestrating Gitea agile workflows with tea CLI) and its triggers, along with explicit non-goals.",{"category":46,"check":138,"severity":30,"summary":139},"Concise Frontmatter","The frontmatter is concise and self-contained, summarizing the core capability and providing trigger phrases effectively within the character limit.",{"category":50,"check":141,"severity":30,"summary":142},"Concise Body","The SKILL.md body is well-structured, under 500 lines, and delegates detailed procedures to separate reference files.",{"category":144,"check":145,"severity":30,"summary":146},"Context","Progressive Disclosure","Detailed procedures and algorithms are delegated to markdown files within the 'references/' directory, linked via relative paths from SKILL.md.",{"category":144,"check":148,"severity":71,"summary":149},"Forked exploration","The skill is workflow-driven and does not involve deep code review or exploration that would necessitate setting 'context: fork'.",{"category":28,"check":151,"severity":30,"summary":152},"Usage examples","Sufficient end-to-end examples are provided, demonstrating invocation patterns and expected flow through checkpoints.",{"category":28,"check":154,"severity":30,"summary":155},"Edge cases","The documentation addresses edge cases and failure modes (e.g., CI failures, merge conflicts, stale worktrees) with recovery steps.",{"category":112,"check":157,"severity":71,"summary":158},"Tool Fallback","The skill relies on git and tea CLI, which are assumed prerequisites and not optional with fallbacks.",{"category":100,"check":160,"severity":30,"summary":161},"Stack assumptions","Stack assumptions (git, Gitea Tea CLI, context network structure) are declared upfront in SKILL.md and prerequisites are listed.",{"category":163,"check":164,"severity":30,"summary":165},"Safety","Halt on unexpected state","The skill's state detection and checkpoint system are designed to halt the workflow on unexpected pre-states and guide the user toward resolution.",{"category":100,"check":167,"severity":30,"summary":168},"Cross-skill coupling","The skill is self-contained for Gitea workflows and does not implicitly rely on other skills, though it references general concepts.",1778053954248,"This skill automates multi-step agile development processes for Gitea, guiding users through task selection, implementation via TDD in isolated worktrees, code reviews, PR creation, and merging. It relies on the Gitea Tea CLI and maintains project state through a context network.","2.0.0","3.4.0","The skill has excellent documentation, clear scope, and robust error handling. However, the critical finding of 'Commit recency' due to no recent commits on the default branch significantly impacts its trustability and production readiness. The 'Release Management' is also a warning due to the version being unreliable.",65,"A comprehensive skill for orchestrating agile development workflows with Gitea repositories using the tea CLI.",[15,16,17,18,19,20],"global","flagged",{"codeQuality":180,"collectedAt":181,"documentation":182,"maintenance":184,"security":185,"testCoverage":188},{},1778053938509,{"descriptionLength":183,"readmeSize":8},460,{},{"hasNpmPackage":186,"license":187,"smitheryVerified":186},false,"MIT",{"hasCi":186,"hasTests":186},{"updatedAt":190},1778054012696,{"githubOwner":192,"githubRepo":193,"locale":24,"slug":194,"type":195},"jwynia","agent-skills","gitea-workflow","skill",null,{"extract":198,"llm":200},{"commitSha":199,"license":187},"e02ec7e226a6e4f8419fd3b88a1d8e472d421b32",{"promptVersionExtension":171,"promptVersionScoring":172,"score":174,"targetMarket":177,"tier":178},{"repoId":202},"kd7efn3mprpa8rd8vm5hw5ebzx864fph",{"_creationTime":204,"_id":202,"identity":205,"providers":207,"workflow":218},1777995558409.897,{"githubOwner":192,"githubRepo":193,"sourceUrl":206},"https://github.com/jwynia/agent-skills",{"discover":208,"github":211},{"sources":209},[210],"skills-sh",{"closedIssues90d":8,"forks":212,"openIssues90d":213,"pushedAt":214,"readmeSize":215,"stars":216,"topics":217},10,2,1771900514000,11924,70,[],{"discoverAt":219,"extractAt":220,"githubAt":220,"updatedAt":220},1777995558409,1778053628601,{"anyEnrichmentAt":222,"extractAt":223,"githubAt":222,"llmAt":190,"updatedAt":190},1778053625386,1778053622473,[],[226,247,266,285,313,332],{"_creationTime":227,"_id":228,"community":229,"display":230,"identity":238,"providers":240,"relations":245,"workflow":246},1778053622473.6682,"k171xwg814163s51767b0q0pn1866cwe",{"reviewCount":8},{"description":231,"installMethods":232,"name":233,"sourceUrl":234,"tags":235},"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",[15,20,236,16,19,17,237],"automation","multi-agent",{"githubOwner":192,"githubRepo":193,"locale":24,"slug":239,"type":195},"gitea-coordinator",{"extract":241,"llm":242},{"commitSha":199,"license":187},{"promptVersionExtension":171,"promptVersionScoring":172,"score":243,"targetMarket":177,"tier":244},98,"verified",{"repoId":202},{"anyEnrichmentAt":222,"extractAt":223,"githubAt":222,"llmAt":190,"updatedAt":190},{"_creationTime":248,"_id":249,"community":250,"display":251,"identity":259,"providers":261,"relations":264,"workflow":265},1778053622473.6672,"k178b0dafhyecx3y6cbxkne8mh866zc4",{"reviewCount":8},{"description":252,"installMethods":253,"name":254,"sourceUrl":255,"tags":256},"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",[16,17,20,257,258,236],"developer-tools","git",{"githubOwner":192,"githubRepo":193,"locale":24,"slug":260,"type":195},"agile-coordinator",{"extract":262,"llm":263},{"commitSha":199,"license":187},{"promptVersionExtension":171,"promptVersionScoring":172,"score":243,"targetMarket":177,"tier":244},{"repoId":202},{"anyEnrichmentAt":222,"extractAt":223,"githubAt":222,"llmAt":190,"updatedAt":190},{"_creationTime":267,"_id":268,"community":269,"display":270,"identity":277,"providers":279,"relations":283,"workflow":284},1778053622473.6677,"k17dkjvzgg6cxjhh7hmz742gq5866hnf",{"reviewCount":8},{"description":271,"installMethods":272,"name":273,"sourceUrl":274,"tags":275},"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",[16,17,258,19,276,20],"task-management",{"githubOwner":192,"githubRepo":193,"locale":24,"slug":278,"type":195},"agile-workflow",{"extract":280,"llm":281},{"commitSha":199,"license":187},{"promptVersionExtension":171,"promptVersionScoring":172,"score":282,"targetMarket":177,"tier":244},95,{"repoId":202},{"anyEnrichmentAt":222,"extractAt":223,"githubAt":222,"llmAt":190,"updatedAt":190},{"_creationTime":286,"_id":287,"community":288,"display":289,"identity":298,"providers":302,"relations":307,"workflow":309},1778053100136.2383,"k1753vf5cqqy17a43rxzq74p09866pde",{"reviewCount":8},{"description":290,"installMethods":291,"name":292,"sourceUrl":293,"tags":294},"Extension from bytedance/deer-flow",{},"DeerFlow Smoke Test","https://github.com/bytedance/deer-flow/tree/HEAD/.agent/skills/smoke-test",[295,19,296,297,17],"testing","docker","bash",{"githubOwner":299,"githubRepo":300,"locale":24,"slug":301,"type":195},"bytedance","deer-flow","smoke-test",{"extract":303,"llm":305},{"commitSha":304,"license":187},"1336872b15c25d45ebcb7c1cf72369c2bdd53187",{"promptVersionExtension":171,"promptVersionScoring":172,"score":306,"targetMarket":177,"tier":244},96,{"repoId":308},"kd789sm7egx1h0t1jag6zzhcq98656wv",{"anyEnrichmentAt":310,"extractAt":311,"githubAt":310,"llmAt":312,"updatedAt":312},1778053101076,1778053100136,1778053169012,{"_creationTime":314,"_id":315,"community":316,"display":317,"identity":325,"providers":327,"relations":330,"workflow":331},1778053622473.6692,"k17e2jngyq2nkmw93gajm8116h867cx5",{"reviewCount":8},{"description":318,"installMethods":319,"name":320,"sourceUrl":321,"tags":322},"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",[323,16,17,19,324,258],"github","cli",{"githubOwner":192,"githubRepo":193,"locale":24,"slug":326,"type":195},"github-agile",{"extract":328,"llm":329},{"commitSha":199,"license":187},{"promptVersionExtension":171,"promptVersionScoring":172,"score":282,"targetMarket":177,"tier":244},{"repoId":202},{"anyEnrichmentAt":222,"extractAt":223,"githubAt":222,"llmAt":190,"updatedAt":190},{"_creationTime":333,"_id":334,"community":335,"display":336,"identity":345,"providers":349,"relations":354,"workflow":356},1778053359436.7288,"k1780yft5sxt8fewxcc5bm1941866rzt",{"reviewCount":8},{"description":337,"installMethods":338,"name":339,"sourceUrl":340,"tags":341},"This skill should be used when the user wants to \"develop an agent\", \"build an agent using ADK\", \"run the agent locally\", \"debug agent code\", \"test an agent\", \"deploy an agent\", \"publish an agent\", \"monitor an agent\", or needs the ADK (Agent Development Kit) development lifecycle and coding guidelines. Entrypoint for building ADK agents. Always active — provides the full workflow (scaffold, build, evaluate, deploy, publish, observe), code preservation rules, model selection guidance, and troubleshooting steps for ADK or any agent development.",{},"ADK Development Workflow & Guidelines","https://github.com/google/agents-cli/tree/HEAD/skills/google-agents-cli-workflow",[342,343,17,344,324],"adk","agent-development","guidelines",{"githubOwner":346,"githubRepo":347,"locale":24,"slug":348,"type":195},"google","agents-cli","google-agents-cli-workflow",{"extract":350,"llm":353},{"commitSha":351,"license":352},"9e2966f509ae8ee8a866cf7ecc6e227209f347ff","Apache-2.0",{"promptVersionExtension":171,"promptVersionScoring":172,"score":243,"targetMarket":177,"tier":244},{"repoId":355},"kd74jrvbwp33xw6azpzkw7r7vs8644t0",{"anyEnrichmentAt":357,"extractAt":358,"githubAt":357,"llmAt":359,"updatedAt":359},1778053359868,1778053359436,1778053387143]