Explore possible next roles from a user's actual tasks, interests, and constraints, including adjacent roles and changes within their current workplace. Build evidence-linked career hypotheses, identify unknown duties and requirements, and propose small ways to test them. Use when someone does not know what work to pursue or asks what they could do beyond their current job; do not diagnose aptitude, rank careers, or predict salary or hiring success.
日本語の概要は準備中です。原文の説明を表示しています。
ficilcom/otame4-work-skills☆ 42026年9月23日 更新
Prepare for a Japanese job interview by working from the documents already submitted: find where an interviewer will dig in (claims the applicant cannot back up, work described in the first person plural, outcomes with no measure, gaps or overlaps in the employment history, must-have requirements the documents never answer), and turn them into questions to prepare evidence for. Use when a user has an interview scheduled and wants to know what will be asked and what to have ready, or wants to prepare reverse questions from earlier company research; do not use to predict whether they will pass, to write answers containing experience they did not report, or to schedule or contact anyone.
日本語の概要は準備中です。原文の説明を表示しています。
ficilcom/otame4-work-skills☆ 42026年9月23日 更新
Review and revise Japanese job-application documents (entry sheets, rirekisho, shokumu-keirekisho) by checking each answer against the question asked, the stated character limit, and the evidence the applicant can actually support, then propose concrete rewrites the applicant decides on. Use when a user wants an ES or resume answer critiqued, tightened, or drafted from their own experience; to assemble a whole shokumu-keirekisho from an experience inventory, use resume-draft instead; do not use to invent experience, to judge pass or fail probability, or to submit an application.
日本語の概要は準備中です。原文の説明を表示しています。
ficilcom/otame4-work-skills☆ 42026年9月23日 更新
Assemble a Japanese shokumu-keirekisho (career history document) from an experience inventory, choosing between reverse-chronological, chronological, and skills-based layouts, mapping the target posting's requirements to the experiences that can support them, and drafting the summary, work history, skills, and self-PR so that each sentence stays within what its evidence supports and confidential details are abstracted. Use when a user wants to write or rebuild a whole shokumu-keirekisho for a specific posting or as a general version, or wants to decide which experiences to include and in what order; do not use to invent experience, numbers, titles, or qualifications, to predict whether it will pass screening, to fill in a rirekisho form, or to submit it anywhere.
日本語の概要は準備中です。原文の説明を表示しています。
ficilcom/otame4-work-skills☆ 42026年9月23日 更新
検査器(linter / ガード / CI ゲート / バリデータ / フィルタ)そのものの検出力が差分で静かに落ちていないか、また新設した検査が実際に検出できることが実証されているかを diff-time で検出する。Check 1 unverified detection reduction(検査器の検出ロジック(正規表現・除外パターン・解決集合・allowlist・baseline)を変更して検出件数が減ったのに、減った 1 件ずつが誤検出であった根拠が示されないまま「誤検出を潰した」「N → M 件に減少」と改善として主張している)、Check 2 unproven guard detection power(新しい検査ロジック・CI ゲート・バリデーションを追加・変更したのに、検出すべき入力を注入して検出されること/検出すべきでない入力で黙ることを示す変異注入の証跡が無く、「追加した」「CI が緑」を検出力の証拠として扱っている)、の 2 Check を対象とする report-only。テスト自身のアサーションが実質何も検証していない構造は test-assertion-effectiveness、レビュー基準・品質ゲートの明示的な弱体化(ルールの削除・閾値の引き下げ・suppression entry 追加・lint ルールの無効化)は review-criteria-integrity、リファクタ完了主張一般の検証は refactor-claim-audit、workflow の permissions と action pin は gha-workflow-security、設定ファイルの構文・型の妥当性は config-json へ委譲する
s977043/river-review☆ 42026年10月12日 更新
Philosophy-first writing partner for Medium with tactical depth. Combines human storytelling values with production-ready technical content tools. Six content modes based on staff pick analysis, mode-specific quality gates, evidence requirements, annotated examples, and comprehensive scripts integration. Designed for sustainable practice, not algorithm gaming.
日本語の概要は準備中です。原文の説明を表示しています。
alirezarezvani/medium-content☆ 42026年4月11日 更新
Durable repo-native multi-goal plans with embedded success criteria and evidence audit.
日本語の概要は準備中です。原文の説明を表示しています。
code-yeongyu/codex-ultragoal☆ 42026年7月26日 更新
Assigns GO terms, Pfam/InterPro domains, KEGG orthologs, EC numbers, and product names to predicted proteins using eggNOG-mapper (orthology), InterProScan (domain signatures), and KofamScan (KEGG), routing specialized functions to dbCAN/antiSMASH/AMRFinderPlus/SignalP. Covers the orthology-vs-domain-vs-homology paradigms, the annotation-error percolation cascade, domain-presence-is-not-function, GO IEA circularity in enrichment, evidence tiering, and bit-score/coverage thresholds. Use when adding functional annotation to predicted genes, choosing between eggNOG-mapper and InterProScan, or judging how much to trust a functional label.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/TRACE☆ 32026年10月11日 更新
Queries ClinVar for variant pathogenicity classifications, ClinGen VCEP curations, and somatic-vs-germline interpretations via REST API, weekly VCF, or bulk XML. Use when determining clinical significance, triangulating conflicting interpretations, or aggregating evidence against the ACMG/AMP framework with ClinGen SVI specifications.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/TRACE☆ 32026年10月11日 更新
Project gene annotations across genomes using TOGA (Kirilenko 2023 whole-genome-alignment chain-based projection with intactness classification), CESAR 2.0 (Sharma & Hiller 2017 codon-aware exon projection), LiftOff (Shumate & Salzberg 2020 reference-based annotation transfer), Liftover (UCSC), GeMoMa (Keilwagen 2019 evidence-based projection), and Comparative Annotation Toolkit (CAT). Use when transferring annotations from a well-annotated reference to query genome(s), classifying gene-loss vs gene-intact across many genomes at scale, building Zoonomia-style comparative annotations across hundreds of mammals or birds (Kirilenko 2023), detecting pseudogenization, projecting alternative isoforms, or selecting between WGA-anchored (TOGA) vs ortholog-based (LiftOff) annotation transfer strategies.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/TRACE☆ 32026年10月11日 更新
Runs cis-pQTL Mendelian randomization for drug-target validation using UKB-PPP (Olink), deCODE (SomaScan), Fenland, INTERVAL, ARIC, and FinnGen-PPP proteomes plus colocalization triangulation, phenome-wide on-target adverse-effect scans, cross-platform Olink/SomaScan replication, and PAV (protein-altering variant) sensitivity. Use when nominating or de-risking a drug target from plasma-proteome GWAS, mimicking pharmacological inhibition via cis-pQTL instruments, separating shared-causal from LD-confounded signal under the Schmidt 2020 cis-MR framework, screening on-target adverse phenotypes pheWAS-style, or producing publication-grade STROBE-MR plus PP.H4 evidence for a target gene.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/TRACE☆ 32026年10月11日 更新
Predicts whether a DNA variant alters mRNA splicing using sequence-based deep-learning tools — SpliceAI (10kb context dilated CNN, clinical default), Pangolin (multi-tissue), MMSplice (modular per-region CNN with calibrated ΔPSI), SpliceTransformer/TrASPr (tissue-aware transformers), SpliceVault (empirical 300K-RNA lookup of likely mis-splicing outcomes), CADD-Splice (composite score). Applies the ClinGen SVI 2023 framework for ACMG/AMP variant interpretation (PVS1, PP3, BP4 evidence codes), HGVS splicing nomenclature (c.123+1G>A, c.123-3T>G, r.spl?), extended-window scoring for deep-intronic pseudoexons, tissue-specific predictions, branchpoint variant detection (BPHunter, LaBranchoR), and splice-switching ASO design. Use when interpreting splice impact of clinical variants, prioritizing VUS, identifying deep-intronic pathogenic variants, or designing ASOs.
日本語の概要は準備中です。原文の説明を表示しています。
peacezha/TRACE☆ 32026年10月11日 更新
Hunt for adversary techniques in telemetry you are authorized to query. Hypothesis-driven, evidence-first, no live offensive operations.
日本語の概要は準備中です。原文の説明を表示しています。
lgzarturo/springboot-course☆ 32026年10月12日 更新
Plan and report authorized vulnerability assessments on owned systems. Prioritize evidence, severity, and remediations. Do not deliver exploit payloads.
日本語の概要は準備中です。原文の説明を表示しています。
lgzarturo/springboot-course☆ 32026年10月12日 更新
Coordinate containment, eradication, and recovery for an authorized incident. Preserve evidence, communicate facts, and avoid destructive actions without approval.
日本語の概要は準備中です。原文の説明を表示しています。
lgzarturo/springboot-course☆ 32026年10月12日 更新
Map controls to SOC2, ISO 27001, PCI, or internal policy for the org you work for. Evidence and control design — not audit theater.
日本語の概要は準備中です。原文の説明を表示しています。
lgzarturo/springboot-course☆ 32026年10月12日 更新
Guides agents through Red-Green-Refactor with runner-captured evidence. Use when running /cc-tdd-cycle, writing tests before implementation, or Global TDD required is yes.
日本語の概要は準備中です。原文の説明を表示しています。
lgzarturo/springboot-course☆ 32026年10月12日 更新
Route agent work through AccInt's MCP memory loop: retrieve prior outcomes, resolve frames, and close commitments with evidence.
日本語の概要は準備中です。原文の説明を表示しています。
phoroth/AGENTIC☆ 32026年8月8日 更新
Audit whether a thesis's stated conviction matches its evidence, and whether any Conviction Trigger has silently fired without being actioned. Use when user says "conviction audit", "is my conviction right on [TICKER]", "did a trigger fire", or "should I re-rate [TICKER]".
日本語の概要は準備中です。原文の説明を表示しています。
jameswong2011/InvestmentVault☆ 32026年9月9日 更新
Use this skill when you need to derive, from web-sourced evidence, typical values for a named plant's annual GPP, LAI, specific LAI or specific leaf area, Rubisco Vcmax at 25oC, Jmax at 25oC, root-to-shoot ratio, rooting depth, leaf protein nitrogen, and leaf chlorophyll nitrogen.
日本語の概要は準備中です。原文の説明を表示しています。
bioepic-data/ecosim-agent☆ 32026年10月12日 更新
Use this skill when deriving EcoSIM plant trait parameter recommendations for a named plant from web and online literature evidence, using a read-only `plant_trait.*.desc` file and the `ndlf43` tree block or `gr3s43` grass block as the starting archetype. Never edit or replace the `.desc` file.
日本語の概要は準備中です。原文の説明を表示しています。
bioepic-data/ecosim-agent☆ 32026年10月12日 更新
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
日本語の概要は準備中です。原文の説明を表示しています。
studiogadget/skills☆ 32026年5月25日 更新
Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
日本語の概要は準備中です。原文の説明を表示しています。
studiogadget/skills☆ 32026年5月25日 更新
Run a bounded, provider-neutral SDD Composy correction loop on one approved task (EXECUTE, QA, EVIDENCE, REVIEW, VERIFY; at most 3 iterations) with explicit approval, safe-stop guards, and fresh verification. Use to continue an approved TASK autonomously — 'rodar o loop na TASK-003', 'continuar a task até passar', 'start a loop on task 4'. Do NOT use for the host's recurring loop runner, for fleets (sdd-fleet), or for a task without human approval.
日本語の概要は準備中です。原文の説明を表示しています。
pwdev-solucoes/pwdev-claude-marketplace☆ 32026年9月28日 更新