{"id":"giuseppe-trisciuoglio-developer-kit","name":"developer-kit","homepage":null,"repo_url":"https://github.com/giuseppe-trisciuoglio/developer-kit","category":"devtools","subcategories":[],"tags":["claude-code","agents","skills-marketplace","specification","task-management","code-review","debugging","multilanguage"],"what_it_does":"Developer Kit for Claude Code: a modular marketplace of plugins (core + language/infra/tooling plugins) that provide reusable skills, agents, and slash commands to drive a repeatable development workflow (brainstorm/spec-to-tasks/task management/feature development/code review & debugging).","use_cases":["Generating functional specifications and acceptance criteria for new features","Decomposing specifications into executable tasks with complexity scoring","Implementing features or executing specific task steps in supported languages/frameworks","Reviewing/refactoring/debugging code against specs and conventions","Standardizing development workflows across teams using Claude Code"],"not_for":["Directly exposing a secure public API for external systems (it is primarily a Claude Code plugin/command system)","Highly regulated environments without verifying plugin behavior and data handling","Use cases requiring strong, explicit authentication/authorization controls from this package alone"],"best_when":"You want consistent, spec-driven engineering workflows inside Claude Code across multiple languages/frameworks using a plugin marketplace model.","avoid_when":"You need a standalone HTTP API/SDK with formal OpenAPI contracts, or you cannot accept that plugin actions (e.g., repo edits, command execution) depend on agent/tool behavior not fully specified here.","alternatives":["Open-source CLI/workflow tools that generate specs and tasks (non-LLM or LLM-assisted) such as custom document generators + issue templates","LangGraph/LangChain-based agent workflows for spec-to-tasks and code review pipelines","Other Claude Code skill/agent packs focused on a single language or single workflow step"],"af_score":39.8,"security_score":17.2,"reliability_score":25.0,"package_type":"skill","discovery_source":["openclaw"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:38:59.771945+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Claude Code / plugin marketplace installation mechanisms (implied)"],"oauth":false,"scopes":false,"notes":"No explicit authentication scheme for the package itself is described in the provided README content. Security model likely depends on Claude Code environment and how plugins execute tools/actions."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing is not described in the provided content."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":39.8,"security_score":17.2,"reliability_score":25.0,"mcp_server_quality":0.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":20.0,"scope_granularity":10.0,"dependency_hygiene":35.0,"secret_handling":25.0,"security_notes":"README indicates a Python pre-tooluse hook `prevent-destructive-commands` to block dangerous Bash commands, which is a positive safety measure. However, no details are provided about how secrets are handled, how credentials are stored, or how permissions/scope boundaries are enforced for plugin actions. The manifest snippet only shows `PyYAML` as a dependency for a different package (`claude-validator`), not for the full developer-kit; dependency hygiene for the full project is therefore unclear from the provided data.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":40.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency guarantees for commands (e.g., whether reruns avoid duplicate files/PRs) are described in the provided content.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Commands may perform destructive operations unless guarded; a hook for blocking dangerous Bash commands is mentioned, but the overall safety boundary is not fully specified here.","Task/spec files are written to repository paths (docs/specs/*); repeated runs could overwrite or create duplicates if not designed to be idempotent."]}}