Results for “te-te”

Write tests for untested OSS code as a standalone contribution. Identifies coverage gaps, studies the repo's test conventions, and guides the user through writing tests that match existing patterns. Use when contributing tests to an open source repo, looking for a low-risk first contribution, or improving test coverage. Not for writing tests alongside a bug fix — use oss-contribute for that.

The English summary is being prepared. Showing the original description.

Generate test files from acceptance criteria or existing code. Supports criteria-driven mode (from specs/tasks) and code-analysis mode (from source files). Auto-detects test framework and spawns test-writer agents for parallel generation.

The English summary is being prepared. Showing the original description.

Create a new team composition file following the agent-almanac team template and registry conventions. Covers team purpose definition, member selection, coordination pattern choice, task decomposition design, machine-readable configuration block, registry integration, and README automation. Use when defining a multi-agent workflow, composing agents for a complex review process, or creating a coordinated group for recurring collaborative tasks.

The English summary is being prepared. Showing the original description.

Phase 2: Generate and discover tests, validate against real library. Only invoke when explicitly requested by the user or by the yoink orchestrator.

The English summary is being prepared. Showing the original description.

Use when asking "overkill?", "elegant?", "audit", or "taste-test this", or setting a taste register. Not for tasks that require source or remote-system changes.

The English summary is being prepared. Showing the original description.

Coordinate the custom Elementor Widget site workflow for kickoff, lightweight company intake, conditional reference research, new-versus-existing site style routing, uncertain next steps, project resumption, or continuous work across content, Design Systems, UI, HTML, and Widget implementation. Do not use for release, old-Widget troubleshooting, theme development, or remote WordPress management.

The English summary is being prepared. Showing the original description.

コードを分析し、テストを段階的に生成・実行

The English summary is being prepared. Showing the original description.

Use when: 会話・設計資料・回答文書から検証タスクを抽出し、別workspaceへ渡すテスト依頼文を作成する。受け手は最初に理解内容と実施項目を返し、承認後に検証する

The English summary is being prepared. Showing the original description.

Use when a task needs the judgment of a Career/Technical Education (CTE) Secondary School Teacher — deciding whether a student is authorized to run a piece of shop equipment, diagnosing a Perkins V industry-credential attainment gap, placing a student into a work-based learning slot, resolving an articulation-credit dispute with a partner college, or triaging a CTSO competition-prep versus baseline-instruction time conflict.

The English summary is being prepared. Showing the original description.

Write unit and integration tests. Use when the user says "write tests for this", "add test coverage", "how do I test this", "TDD", "red green refactor", "unit test this function", "test this module", "I need tests for", or has code that lacks tests - even if they don't explicitly say "write tests".

The English summary is being prepared. Showing the original description.

Update PROJECT_CONTINUITY.md and notes.toml with current session state. Use proactively before context compaction or when switching tasks.

The English summary is being prepared. Showing the original description.

Fallback for general coding work that does not match any specific sextant sub-skill. Use for lightweight tasks: config changes, style fixes, utility functions, one-off scripts, or tasks too small to warrant a dedicated workflow. All dedicated sub-skills take priority over this one — check these first: sextant:fix-bug (broken behavior), sextant:debug (unknown bug location), sextant:add-feature (new functionality), sextant:modify-feature (changing existing behavior), sextant:review-code (evaluating code), sextant:write-tests (test coverage), sextant:refine-requirements (ambiguous scope), sextant:plan (multi-step sequencing), sextant:ship (release prep), sextant:migrate (cross-module upgrade), sextant:security (vulnerability audit). Only use this skill when none of the above match.

The English summary is being prepared. Showing the original description.

Write meaningful Replica tests. Use when adding regression coverage, testing new behavior, or changing existing automated tests.

The English summary is being prepared. Showing the original description.

Evaluates basal insulin rates through basal rate testing across different time periods and adjusts as indicated. Triggered by clinician orders to 'Perform basal rate test to verify pump settings' or 'Check basal rates during periodic pump review'.

The English summary is being prepared. Showing the original description.

How to run tests using remote executor.

The English summary is being prepared. Showing the original description.

Write automated tests for unticked scenarios in this card's test cases

The English summary is being prepared. Showing the original description.

Builds a slide-by-slide presentation draft on the user's own slide template and checks every slide against written brand rules (colours with hex codes, fonts, logo placement, slide archetypes, tone, banned visuals), returning the approved outline, the DRAFT deck content and a compliance report as Markdown. Use when the user asks to "build this deck on our template", "make these slides on-brand", "check this presentation against our brand guidelines", "rebuild these slides to corporate identity (CI)" or asks for a CI-compliant or corporate-template presentation. Do not use for an accessibility review of slides, use document-accessibility-check instead. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (August 2022 edition 8.02) with DOT&E-facing enterprise emphasis. Use for T&E enterprise roles (DOT&E vs USD(R&E)), DT&E/OT&E/LFT&E, cybersecurity T&E, MOSA/automation/digital enablers, suitability/reliability growth, and TEMP/Strategy/STE planning. Distinct routing from dod-te-guidebook (same guidebook family, pathway-deep pack). Guidance only—defer to DoDI 5000.89 and Title 10 for binding requirements.

The English summary is being prepared. Showing the original description.

Parallel geführte Sprachfassungen eines Dokuments (Paper DE/EN, README + README_de, SKILL.md + SKILL.en.md, Website-Texte) synchron halten: fehlende Fassung nachziehen, Abschnitts-Parallelität prüfen, Divergenzen beheben — mit klarer Leitsprache-Regel und kontrolliertem Rücktransfer, wenn die Nebenfassung etwas besser löst. Nutze diesen Skill bei „sind DE und EN synchron?", „zieh die englische/deutsche Version nach", „Übersetzung ist veraltet", bei zweisprachigen Papers/READMEs/Skills, oder als periodischen Check über einen Dokumentbestand. Enthält auch das Expansions-Audit: bewerten, ob ein Projekt/Dokument WEITERE Sprachen verdient (i18n-Eignung nach Zielgruppe, technische Vorbereitung, kein blindes Massenübersetzen).

The English summary is being prepared. Showing the original description.

This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp ...

The English summary is being prepared. Showing the original description.

Expert en technologies climatiques avancées (carbon accounting, ESG reporting, offset verification, DZ context)

The English summary is being prepared. Showing the original description.

Expert en climate tech (carbon accounting, ESG, sustainability reporting, green tech)

The English summary is being prepared. Showing the original description.

Execute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows.

The English summary is being prepared. Showing the original description.

HTTP Request Smuggling — frontend/backend HTTP parser uyumsuzluğunu sömürerek auth bypass, cache poisoning, internal endpoint erişimi

The English summary is being prepared. Showing the original description.